search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
162.37k stars 28.61k forks source link

Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006) #115818

Closed quyleanh closed 3 years ago

quyleanh commented 3 years ago

Steps to Reproduce:

  1. Enter code . command on a folder on WSL2
  2. The error is thrown
Could not fetch remote environment
Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)

VSCode version 1.52.1 does not have this issue.

Does this issue occur when all extensions are disabled?: Yes

DenisYaroshevskiy commented 3 years ago

Same issue with plain remote access. Related to the sftp extension.

Entoryvekum commented 3 years ago

Updating Remote-WSL to 0.53.4 didn't solve the problem,but restarting wsl itself has a probability to work.

alecthegeek commented 3 years ago

So it turns my problem was in WSL2 because I had compressed the NTFS $env:TEMP directory.

See https://github.com/microsoft/WSL/issues/5286#issuecomment-638739724

Now works again Phew!

quyleanh commented 3 years ago

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.

christopherobin commented 3 years ago

0.53.3 works for me but 0.53.4 seems broken, downgrading to 0.53.3 using the VSIX file on both host and WSL fixes the issue here

trallnag commented 3 years ago

@quyleanh, can you reopen? Or should we create a new issue

trallnag commented 3 years ago

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.

trallnag commented 3 years ago

Also I just noticed hundreds of socket connections in my /tmp directory

srwxr-xr-x  1 jfn  jfn         0 Jan 22 11:04 vscode-ipc-e744dfff-2b84-46e3-96df-5254d37294ed.sock=
srwxr-xr-x  1 jfn  jfn         0 Dec 22 12:25 vscode-ipc-e8930ca7-2a06-4330-81ea-70a743593844.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 22 11:52 vscode-ipc-ebab54a1-42c7-45ae-97e1-a857d855ad1b.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 26 12:35 vscode-ipc-ec6a760f-d4f1-4058-a7e3-69254fbc602b.sock=
srwxr-xr-x  1 jfn  jfn         0 Dec 21 18:00 vscode-ipc-ed1cbbc5-9972-4264-947f-ca9af7958c50.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 18 14:20 vscode-ipc-eea7cbb8-738e-4c19-842b-f3cd3ad7af7e.sock=
srwxr-xr-x  1 jfn  jfn         0 Nov 25 16:06 vscode-ipc-ef19b9fb-1785-4024-bf65-5f29aea0a502.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 11 09:28 vscode-ipc-eff935c7-ed3c-40e7-8190-efeedbe3edeb.sock=
srwxr-xr-x  1 jfn  jfn         0 Dec  2 08:41 vscode-ipc-f00e6d57-b9cc-4ad5-b170-ffbc447d2dbd.sock=
srwxr-xr-x  1 jfn  jfn         0 Nov 22 16:42 vscode-ipc-f0ecd1c0-41e2-4a42-92f4-e158dd3f4356.sock=
srwxr-xr-x  1 jfn  jfn         0 Nov 27 11:00 vscode-ipc-f161c90e-1fcd-44d1-a451-c1f1ada8e867.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 19 00:45 vscode-ipc-f20c7761-f316-450c-bf23-47e701f7a421.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 21 14:48 vscode-ipc-f3b520dc-5c23-46a9-801f-fa83c44c7f3c.sock=
srwxr-xr-x  1 jfn  jfn         0 Dec  5 13:46 vscode-ipc-f52a7b0c-5b8f-4440-a4e7-eb4a7e8815ea.sock=
srwxr-xr-x  1 jfn  jfn         0 Nov 24 09:50 vscode-ipc-f750d47c-9243-4a1d-b3fb-6e1aaf0805f8.sock=
srwxr-xr-x  1 jfn  jfn         0 Feb  6 15:30 vscode-ipc-f781f2dc-8efe-4658-a029-8fece16b11df.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 29 12:45 vscode-ipc-f9563aea-e42e-458c-a1d4-b241882518ef.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 11 09:27 vscode-ipc-f984bfbd-d13a-4118-9f0c-f99f8fb86f98.sock=
srwxr-xr-x  1 jfn  jfn         0 Dec 19 14:10 vscode-ipc-fa78f6c2-22a8-4bb2-94da-d98d93881ac4.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 27 22:44 vscode-ipc-fb8d9af6-aa2d-45e8-97c1-e39b9826250f.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 28 12:31 vscode-ipc-fd61865d-07f3-4cb5-9c30-53f3b6275cb2.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 19 02:10 vscode-ipc-fde1a2aa-fd3b-461c-882c-37c388a5ac0b.sock=
srwxr-xr-x  1 jfn  jfn         0 Jan 20 12:38 vscode-ipc-fed1eaaa-001c-4d3a-9b1c-99a2b8929760.sock=
quyleanh commented 3 years ago

@trallnag ok, I will reopen this issue.

In my computer, the loading speed is very slow.

wicked1133 commented 3 years ago

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.

trallnag commented 3 years ago

@wicked1133, uninstall the code server or check your tmp directory (or whatever directory is used) and delete all sockets used by VS code

kinekt4 commented 3 years ago

I'm also running a proxy and had this problem. Some of the things I've tried:

However, I found that setting Http: Proxy Support to override (without proxy exception, or extension config changes) now seems to work as well.

aeschli commented 3 years ago

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 @wicked1133 This issue is not really related to Remote SSH @christopherobin In 0.53.3 , "remote.WSL.server.connectThroughLocalhost" is true by default, in 0.53.4 it's false

VietMa9997 commented 3 years ago

This did the job for me: I closed both Linux WSL tab and VsCode, them I opened a command prompt (with admin priviligies) and used this: wsl --shutdown After that I opened my linux tab again, type "code ." and... after a minute it worked for me. I hope this help you out.

Thanks, this worked for me !

nisaji commented 3 years ago

Convert WSL2 Distoribution to WSL one solved this problem.

roeniss commented 3 years ago

0.65.1 : FAIL 0.51.0 : SUCCESS (after rm -rf .vscode-server from remote server)

JohnHind commented 3 years ago

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.

cool-delete commented 3 years ago

Hi, after updating to the Remote-WSL extension 0.53.4 and adding the parameters the base environment seems to be working again, but the debugging is totally broken, by default the container cannot longer see the WSL host, so xDebug can't connect, and when the IP actually resolves and the container gets to connect to VsCode, the debug won't work as expected, just some breakpoints work, and full of "error evaluating code"

Also would like to add that after the update my settings.json is clean, what contents should it have?

in contrast set true ✔

AntoCanza commented 3 years ago

i'm facing the same issue.

vscode 1.55.1 remote-containers v0.166.1

tried many of the steps suggested before... but nothing is working