I’ve been using VS Code with WSL2 (Ubuntu) for my coursework. Everything worked fine until about a week ago. Now, whenever I try to open VS Code in WSL, it fails to connect.
Errors I see in the logs:
WebSocket close with status code 1006 (connection timeout)
navigator is now a global in nodejs (Remote-WSL extension error)
What I’ve already tried:
Restarted computer, disconnected/reconnected Wi-Fi
wsl --shutdown and restarted WSL2
Uninstalled and reinstalled VS Code and the Remote-WSL extension
Deleted .vscode-server inside WSL
Uninstalled/reinstalled Ubuntu distro (wsl --unregister Ubuntu)
netsh winsock reset, ipconfig /flushdns on Windows
Verified WSL reports as healthy (wsl --status)
Environment:
Windows 11 build 26100
WSL2, Ubuntu 24.04
VS Code 1.xx.xx (stable)
Remote - WSL extension v0.104.2
It seems like the VS Code server starts in WSL, but VS Code on Windows can’t connect via loopback (127.0.0.1). Even running a simple Python http.server in WSL and trying to curl 127.0.0.1:8080 from Windows times out.
Question:
Has anyone else hit this after recent Windows/WSL updates? Is there a way to fix the Windows ↔ WSL loopback proxy so VS Code can connect again?