-
Notifications
You must be signed in to change notification settings - Fork 313
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-SSH Bug]: Could not establish connection when useExecServer
is false
#10229
Comments
Seeing similar issue, but seeing |
As a workaround, Downgrading vscode itself to 1.92.2 works for me https://code.visualstudio.com/updates/v1_92 |
An alternative is to downgrade the plugin to |
Looks like an issue with
and can also be worked around by setting to |
Issue #10208 looks like a similar problem |
Thanks for opening. It looks like I missed a case when |
IIRC the reason I have |
Yes, that's likely :) The |
useExecServer
is false
Yes, setting it back to default does resolve the original issue. Thx. |
Thank you for trying again and letting me know @shiltian |
Setting |
Release patch version |
I run an Ubuntu server where multiple VSCode users SSH remote into, and they all use the
However, we all also had VSCode stall on "Downloading VSCode Server". Around the same time, I also noticed that the We set I hypothesized that the root cause was how VSCode managed the relative path, so I tried a few things. Ultimately, I found that using
VSCod server installed first try with no issues, and my install path is the expected:
Everything seems to work correctly for me now. |
Steps to Reproduce:
No extra step needed. Just simply connect to any remote.
The text was updated successfully, but these errors were encountered: