VSCode Remote Slow Ring ECONNREFUSED

[bushidocodes]

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.

If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.

Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\

See our contributing instructions for assistance.

Please fill out the below information:

• Your Windows build number: (Type ver at a Windows Command Prompt)
  Microsoft Windows [Version 10.0.19018.1]

• What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

VSCode occasionally gets in an error state where it can't connect to WSL. I have to reboot to resolve this, as the behavior is seemingly non deterministic. This is described in the issue I filed against the VSCode Remote Repo: microsoft/vscode-remote-release#1841

Please refer there for screenshots and descriptions, as other users have posted additional information there. In short, the VSCode Remote extension is occasionally failing to be able to connect to WSL2.

The maintainers there suggested this is likely a WSL bug and should be filed here.

• What's wrong / what should be happening instead:

I expect that VSCode should always be able to connect to WSL without error.

• Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).

• For WSL launch issues, please collect detailed logs.

I am going to collect networking logs via Feedback hub momentarily.

[derrix060]

The problem is also happening on Microsoft Windows [Version 10.0.19025.1]

[FabienDehopre]

This also happens on fast ring on Microsoft Windows [Version 10.0.19037.1]

[tlthiem]

While I have the same issue I am able to get rid of it by simply restarting WSL using PowerShell.
PowerShell command: wsl --shutdown; wsl No need to restart my system.

[benjamin-bader]

Happened to me on OS build 19536.1000, but rebooting resolved it. A Heisenbug, it seems. wsl --shutdown; wsl did not resolve it in my case.

[bastos]

Happened to me two times on 19536.1000 (slow ring), this is the log from one of the times:

[2019-12-23 13:58:53.432] Resolving wsl+Ubuntu, resolveAttempt: 1
[2019-12-23 13:58:53.489] Starting VS Code Server inside WSL (Ubuntu)
[2019-12-23 13:58:53.489] Extension version: 0.41.6, Windows build: 19536. Multi distro support: available. WSL path support: enabled
[2019-12-23 13:58:53.644] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e sh -c "[ -d ~/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0 ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2019-12-23 13:58:53.766] Probing result: found
[2019-12-23 13:58:53.766] Server install found in WSL
[2019-12-23 13:58:53.766] Launching C:\WINDOWS\System32\wsl.exe -d Ubuntu sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 26076a4de974ead31f97692a0d32f90d735645c0 stable .vscode-server 0  ' in c:\Users\basto\.vscode\extensions\ms-vscode-remote.remote-wsl-0.41.6
[2019-12-23 13:58:53.945] Setting up server environment: Looking for /home/bastos/.vscode-server/server-env-setup. Not found.
[2019-12-23 13:58:53.945] WSL version: 4.19.81-microsoft-standard Ubuntu
[2019-12-23 13:58:53.946] WSL2-shell-PID: 16332
[2019-12-23 13:58:53.946] Starting server: /home/bastos/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0/server.sh  --port=0 --enable-remote-auto-shutdown 
[2019-12-23 13:58:54.254] 
[2019-12-23 13:58:54.254] 
[2019-12-23 13:58:54.254] *
[2019-12-23 13:58:54.254] * Visual Studio Code Server
[2019-12-23 13:58:54.254] *
[2019-12-23 13:58:54.254] * Reminder: You may only use this software with Visual Studio family products,
[2019-12-23 13:58:54.254] * as described in the license https://aka.ms/vscode-remote/license
[2019-12-23 13:58:54.254] *
[2019-12-23 13:58:54.254] 
[2019-12-23 13:58:54.254] 
[2019-12-23 13:58:54.254] IP Address: 172.27[[REDACTED]]
[2019-12-23 13:58:54.254] Extension host agent listening on 35191
[2019-12-23 13:58:54.254] 
[2019-12-23 13:58:54.254] 
[2019-12-23 13:58:54.254] [10:58:53] Extension host agent started.
[2019-12-23 13:58:54.256] WSL resolver response: ::1:35191
[2019-12-23 13:58:54.256] To debug connection issues, open a local browser on http://[::1]:35191/version

[arif-b-khan]

While I have the same issue I am able to get rid of it by simply restarting WSL using PowerShell.
PowerShell command: wsl --shutdown; wsl No need to restart my system.

Thank a lot you suggestion helped me solve this issue.

[benhillis]

/dupe #4636

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!