-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006) #115818
Comments
(Experimental duplicate detection) |
I too, have the same issue mentioned. Does this have something to do with the latest update? |
Same here, but with another two extensions: SFTP explorer, and SSH, also in recent update of vsc 1.53.0 |
Looks related to #115859 |
It doesn't seem directly related to any specific extension for me (I don't even have SFTP installed, and I removed all extensions just in case). I had this break in insiders last month and it hasn't worked since. Latest update (1.53) to code broke my code in the same way. Multiple people in our company are seeing the same issue. Starting code in WSL 2 gives: Only useful logs I see are from the Log (Window) Output:
Running WSL extension with debug info I see For reference the full debug logs from the extension host are here:
|
I have the same issue. Downgrading to 1.52.1 solved the problem. Maybe is related with this issue #105536 OS: Windows_NT x64 10.0.18362 |
@pppetrov That's the log when a windows connects to a remote server that is already running (started be another window). |
@aeschli sorry first time debugging vscode :) not well versed in the internals. So I just closed everything and confirmed their is not running code related process in wsl2. Started it from the wsl 2 shell with
When vscode launches I get the error: Log (Extension Host)
Log (Main)
Log (Shared)
I suspect the WSL log you are referring is something else? Any pointers on how I can get that? Couldn't figure it out from the docs I found |
Thanks a lot, these logs might also be helpful. But yes, the WSL log is another log. Run the |
Aah got it! Here the logs when running
|
How to downgrade? Where I can download 1.52.1 version? Thanks |
|
@NormandoHall You can get the old version here. (tip make sure you disable automatic updates if you have them on) |
The change we did in 1.53 is that we have moved from using the nodejs TCP/IP stack (we were previously using the It looks like in this particular case WSL responds with a non-loopback (127.0.0.1) IP address: cc @joaomoreno if you have some advice on how to troubleshoot this. @pppetrov Could you perhaps validate that this is somehow proxy related? Like is it possible for you to disable your proxy settings or perhaps disable your wifi/network connection to see if that makes any observable difference? |
@alexdima Disabling the proxy did it! Isolated to:
Thanks for this! Hopefully we can figure out how to deal with a proxy. I will play around with stuff on my WSL side although I'm not too well versed in this stuff. |
@pppetrov Thanks, disable proxy settings in vscode settings fixed issue. |
@chrmarti I am not very familiar with VSCode's proxy support. Is there something I need to do on my side to support proxies? I am simply constructing a |
I have Windows configured to use a SOCKS proxy (at the operating-system level, rather than within vscode). With the proxy disabled the WSL folders show correctly, but with the proxy enabled the folder fails to open as described by others in this thread. Is it possible to ask VSCode to ignore my system proxy settings when communicating with WSL? |
I can confirm this. If I don't disable proxy completelly, vscode can't connect wit WSL. I tried ignore wsl's IP in proxy config but it can't connect anyway. |
I've got the exact same issue here with version 1.53. Configuring the http proxy support to off doesn't change anything for me. |
Starting with |
@deepak1556 Do you know if there is a way to update the proxy bypass list programmatically without overwriting the configured proxy? I have tried with |
This did the job for me: |
This is my log with "remote.WSL.server.connectThroughLocalhost" disabled: [2021-02-11 07:10:36.107] IP Address: 172.17.16.61 I am behind a corporate proxy configured at os level. I tried to ignore explicitly the range of ips that wsl is using but it doesn't work either. |
Thanks a lot for your response, and it would fix the issue temporarily, and after one or 2 restarts of my containers the communication would break again, also debug will work fine, then go totally crazy, I created a separate ticket for this particular issue |
Hi, I'm having the same issue with Linux as well |
Same issue with plain remote access. Related to the sftp extension. |
Updating Remote-WSL to 0.53.4 didn't solve the problem,but restarting wsl itself has a probability to work. |
So it turns my problem was in WSL2 because I had compressed the NTFS $env:TEMP directory. See microsoft/WSL#5286 (comment) Now works again Phew! |
Since the latest Remote-WSL extension (0.53.4) and VSCode (1.53.2) solve the problem, I would like to close this issue. However, does anyone notice about slow start? In my machine, VSCode take long time to start. |
|
@quyleanh, can you reopen? Or should we create a new issue |
Just run into the same issue with 0.53.4. Only way to fix this for me is to reinstall the code server. Then it starts to work again. Reoccurred directly after my W10 network connection (for whatever reason) did a reset / restart. |
Also I just noticed hundreds of socket connections in my /tmp directory
|
@trallnag ok, I will reopen this issue. In my computer, the loading speed is very slow. |
This issue still happens to me with the latest version 1.53.2 and I can't figure out a way to get my Remote SSH working again. |
@wicked1133, uninstall the code server or check your tmp directory (or whatever directory is used) and delete all sockets used by VS code |
I'm also running a proxy and had this problem. Some of the things I've tried:
However, I found that setting
|
Please create new issues. It's complicated to keep things separate Please always describe if you are behind a proxy, if you have "remote.WSL.server.connectThroughLocalhost": true or false and what the WSL log shows. @trallnag There are temp files that should be cleared at some points |
Thanks, this worked for me ! |
Convert WSL2 Distoribution to WSL one solved this problem. |
0.65.1 : FAIL |
I had this problem too and following some of the hints in these comments I remembered I had ExpressVPN connected. I disconnected the VPN, executed 'Remote-Containers: Reopen Locally' then 'Remote-Containers: Reopen in Container'. After this it worked correctly. This is all with 1.54.3 of VSCode and 0.163.2 of Remote-Containers. |
in contrast set true ✔ |
i'm facing the same issue. vscode 1.55.1 tried many of the steps suggested before... but nothing is working |
Steps to Reproduce:
code .
command on a folder on WSL2VSCode version 1.52.1 does not have this issue.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: