Open amadanmath opened 1 month ago
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Multiple log files found, using: https://github.com/user-attachments/files/17071750/WslNetworkingLogs-2024-09-20_16-34-16.zip
.wslconfig found
Detected appx version: 2.2.4.0
optional-components.txt not found
Most of the linked issues have no answers; those that do, do not work for me.
Interestingly, if I run a server inside WSL, it can be accessed from outside:
$ # WSL
$ nc -l 8000
and
> REM cmd.exe
> curl http://localhost:8000
I can also do the reverse, though only by using 192.168.0.1
(address of vEthernet (WSL (Hyper-V firewall))
) instead of localhost
. But I cannot get a response from any other server.
My flask inside WSL suddenly stopped working after I updated windows. I can ping out form WSL just fine, but If I try to connect to the flaks server via the browser, I get connection refused.
My flask inside WSL suddenly stopped working after I updated windows. I can ping out form WSL just fine, but If I try to connect to the flaks server via the browser, I get connection refused.
I uninstalled windows update: "2024-09 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5043076)"
and that fixed it. I can access the loopback interface through wsl again. However, now my start menu does not work..
Windows Version
Microsoft Windows [Version 10.0.22631.3880]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Expected Behavior
Something similar to
Actual Behavior
NOTES:
TCP/IP in WSL worked when I first installed it. It broke later; I am not sure why. It may have been because Norton 360 For Gamers activated; I have uninstalled it since. It may have been because I installed Docker inside WSL Ubuntu. I have since made a clean reinstall of WSL, with no packages installed (except net-tools,. which I managed to install from
dpkg
downloaded from Windows), and it is broken. I have tried installing and uninstalling Hyper-V (from Turn Windows Features On or Off). I have disabled Fast Restart. I have seen decompressing all files suggested, so I tried that as well. I have also disabled swap in.wslconfig
. None of these resolved the problem.I saw some other issues on WSL connectivity, where the suggested remedy is setting nameserver. This is unrelated, the numeric IPs don't work.
Here is some more output I have collected:
and on the host Windows cmd:
Diagnostic Logs
WslNetworkingLogs-2024-09-20_16-34-16.zip WslLogs-2024-09-20_16-35-48.zip