WSL2 connectivity issues with build 19536

[meatherly]

Issue Type: Bug

The error pop up shows:
Unable to open 'my-app': Unable to read file (Error: connect ECONNREFUSED ::1:43283).

I also don't have any of my installed extensions. Please let me know if there is anything I can do to help you guys debug the issue.

VS Code version: Code 1.41.0 (9579eda04fdb3a9bba2750f15193e5fafe16b959, 2019-12-11T18:37:42.077Z)
OS version: Windows_NT x64 10.0.19536
Fetching remote diagnostics for 'WSL: Ubuntu' failed: connect ECONNREFUSED ::1:43283

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2208)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off surface_control: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.72GB (7.05GB free)
Process Argv
Screen Reader	no
VM	0%

Fetching remote diagnostics for 'WSL: Ubuntu' failed: connect ECONNREFUSED ::1:43283

Extensions: none

[meatherly]

This is what is in my hosts file on windows
one of them has:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost
192.168.2.236 host.docker.internal
192.168.2.236 gateway.docker.internal
172.16.0.64 host.docker.internal
172.16.0.64 gateway.docker.internal
192.168.2.235 host.docker.internal
192.168.2.235 gateway.docker.internal
172.16.0.165 host.docker.internal
172.16.0.165 gateway.docker.internal
 host.docker.internal
 gateway.docker.internal
172.16.1.88 host.docker.internal
172.16.1.88 gateway.docker.internal
# Added by Docker Desktop
10.0.0.7 host.docker.internal
10.0.0.7 gateway.docker.internal
# To allow the same kube context to work on the host and the container:
127.0.0.1 kubernetes.docker.internal
# End of section

What is really strange is that if I shutdown wsl2 to and then start it backup code will work but then trying to connect to localhost from windows doesn't. It's either one or the other works. Either I can connect to an app running on wsl from windows or I can use code to edit file on wsl but I can't do both. 🤔

Trying to give you guys as much info as I can.

[meatherly]

Today I tried restoring my windows instance by using the restore tool and after it was done restoring it removed Windows insiders preview 15536.1000 and the issue went away. I'll try reinstalling that version to see if the problem comes back.

[meatherly]

After installing the update it seems like the problem is back. I can launch code and it connects to the folder but when I run nc -lk 0.0.0.0 3000 | bash and try to access it from the windows side with chrome localhost:3000 I can't.

[aaronpowell]

I think there may be a problem with the 19536.1000 build of Windows as I'm hitting problems with wsl2 networking which is seen as things like the extension can't find the remote instances and when running something from wsl2 the port(s) aren't exposed.

[aaronpowell]

cross referencing a potentially relevant WSL issue microsoft/WSL#4769

[brennaman]

I restored Windows to the version prior to 19536.1000 and my WSL issue went away as well.

[slooker]

I restored Windows to the version prior to 19536.1000 and my WSL issue went away as well.

How did you restore? I'm running into the same issue right now and can't seem to figure out how to go back to the old build.

[brennaman]

@slooker to restore to previous version go to Windows Settings -> Update & Security -> Recovery. From there you should see a section "Go back to the previous version of Windows 10".

[aeschli]

dup of #2060

It's a WSL2 issue.
I just released a new version of the extension - Remote - WSL 0.42.1 - that should work around the issue. It requires VSCode Insiders (1.42.0). It would be great if you can give it a try. If it works I can also make a version for the stable VSCode (1.41.1).

[aaronpowell]

@aeschli looks like the latest update resolves the problem (running Win10 19536 and VS Code Insiders 1.42.0).

[bplasmeijer]

No issue anymore with (Remote - WSL 0.42.1) @aeschli ; I did test the sleep and hibernate mode.

Thanks a lot.
Bart

[oorestisime]

Same here, issue fixed with the new version.

[gualterandre]

I can confirm as well. Fixed with VC Code Insiders. Waiting on VSCode stable release.

[Nathan-Furnal]

Hi, will we see a quick patch for VS Code proper or do we have to wait until the update?

Thanks for the good work

[aeschli]

I just published Remote - WSL 0.41.7 that works with VSCode Stable (1.41.x).

[Nathan-Furnal]

Thanks a ton ! I’ll install it asap Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10

…

________________________________ De : Martin Aeschlimann <notifications@github.com> Envoyé : Tuesday, January 7, 2020 5:04:35 PM À : microsoft/vscode-remote-release <vscode-remote-release@noreply.github.com> Cc : Nathan Furnal <nathan_furnal@hotmail.com>; Comment <comment@noreply.github.com> Objet : Re: [microsoft/vscode-remote-release] WSL2 connectivity issues with build 19536 (#2060) I just published Remote - WSL 0.41.7 that works with VSCode Stable (1.41). — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#2060?email_source=notifications&email_token=AK34HBFHNKBBJAXAQWPTSWDQ4SRZHA5CNFSM4J5CIVLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIJLLJI#issuecomment-571651493>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AK34HBF4IOUC47UJXAPIHCLQ4SRZHANCNFSM4J5CIVLA>.