[GH-ISSUE #45] [Suggestion] Add a disclaimer about firewall debugging in the README.md #38

Closed
opened 2026-03-04 12:24:08 +03:00 by kerem · 1 comment
Owner

Originally created by @LouizFC on GitHub (Oct 6, 2021).
Original GitHub issue: https://github.com/cascadium/wsl-windows-toolbar-launcher/issues/45

Greetings.

I found out this repo while trying to configure a x11 server with wsl2. From my research, this repo is one of the main sources that people are currently pointing to when trying to help others.

That said, I had a problem discovering which port I needed to add in the firewall rule ,I created the rule for port 6000, but after enabling firewall logs, I discovered that the server was running in 6001.

I also had a problem with the DISPLAY variable, my x server was running on :1.0 instead of :0.0.

I think that a mini-guide of how to enable firewall logs and a disclaimer to check the x server connection url would be very helpful to people coming to this repository with this kind of problem, so before I open a PR, I wanted to know if this kind of information is in the scope of this repo.

Originally created by @LouizFC on GitHub (Oct 6, 2021). Original GitHub issue: https://github.com/cascadium/wsl-windows-toolbar-launcher/issues/45 Greetings. I found out this repo while trying to configure a x11 server with wsl2. From my research, this repo is one of the main sources that people are currently pointing to when trying to help others. That said, I had a problem discovering which port I needed to add in the firewall rule ,I created the rule for port 6000, but after enabling firewall logs, I discovered that the server was running in 6001. I also had a problem with the `DISPLAY` variable, my x server was running on :1.0 instead of :0.0. I think that a mini-guide of how to enable firewall logs and a disclaimer to check the x server connection url would be very helpful to people coming to this repository with this kind of problem, so before I open a PR, I wanted to know if this kind of information is in the scope of this repo.
kerem closed this issue 2026-03-04 12:24:08 +03:00
Author
Owner

@fquinner commented on GitHub (Jan 5, 2022):

Just replaced:

TCP port 6000 (most likely)

With:

TCP port 6000 (most likely, but verify with display number / X11 server documentation before continuing)

I think that's all that realistically we can do here without documenting every X11 server which I would rather avoid. Thanks for pointing out.

<!-- gh-comment-id:1005806549 --> @fquinner commented on GitHub (Jan 5, 2022): Just replaced: TCP port 6000 (most likely) With: TCP port 6000 (most likely, but verify with display number / X11 server documentation before continuing) I think that's all that realistically we can do here without documenting every X11 server which I would rather avoid. Thanks for pointing out.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/wsl-windows-toolbar-launcher#38
No description provided.