-
Notifications
You must be signed in to change notification settings - Fork 293
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
Remote WSL 0.63.11 'Failed to connect to the remote extension host server' #6067
Comments
@aeschli
and on the other:
im not getting any more content |
@Bentzeh I see a problem in the log: ' --connection-secret=` To get more logging, can you add the setting |
The second log is the interesting one (The one that starts the server). As you see it starts in the middle of the line. There should be more logging before that. Now I see that Do you still see the issue? |
I'm getting what I presume is related. Same version 0.63.11.
|
regarding i'm still experiencing the issue. this is the content of the terminal after i added
|
If it helps anyone temporarily, rolling back to Edit: After others have had success with |
I've downgraded to thanks |
Thanks @Bentzeh for the log! I'd be happy if you can help me figuring this one out... When you run |
@aeschli |
Same here |
@Bentzeh Are you in a WSL window? |
@aeschli |
Ok, I see, sorry I thought the remote log would be available then, but looks like not. |
The log has that testing link (e.g. |
not working |
If you set the setting |
when i add looks like it works should I leave it like that? or should I wait for some fix |
Did not work in my case. Only downgrade to 0.63.4 helped. |
You can leave it as workaround. I still try to find out what the problem is. With
That seems to fail. Is there anything special with your distro. Proxy settings, firewall? |
I was having the same problem until I rolled back to 0.63.5. We have a particularly stupid firewall configuration imposed by IT that blocks all ports on the Windows side of the WSL2 virtual network connection. |
0.63.12 works like a charm. Thanks a lot for your work! |
there isn't any special "config" I'm aware of I've tried to upgrade to |
I published |
thanks :) |
@aeschli |
Awesome. Thanks a lot for your help! I'm wondering: what do you have in your |
|
|
@grnkvch Are you on WSL1 or WSL 2? Did you enable polling? Can you provide the WSL log? I suggest to do that in a new issue as I don't think the two issues are related, |
Since I on WSL 2, I thought I don't need to enable polling I guess, since problem occures recently it probably related with changes after v0.63.5 WSL log
|
Correct, polling is only for WSL1. |
@aeschli |
I'm working in linux fs (/home/user/projectFolder), all watchers are working correctly (eg pm2 or webpack), exept VS Code source control |
@Bentzeh I'm not saying it is wrong, but typically |
@aeschli any steps to verify. |
|
Hi I've just updated docker desktop and vscode
and I'm getting
Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)
not sure what is the
WSL log
but here is the content ofshow log
as explained abovethe first time I've got:
the second time I've run the commend I got
and the content of
wsl.exe --list --verbose
Originally posted by @Bentzeh in #6031 (comment)
The text was updated successfully, but these errors were encountered: