-
Notifications
You must be signed in to change notification settings - Fork 325
Can't connect to Remote SSH server using Exec server #10939
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
Comments
Thanks for the details. You're saying that files in
Note that:
If that file is not there, that's the problem 🤔 That file needs to exist so the extension can parse out a port number If for some reason your home directory isn't writeable, you can change the directory used with |
It exists, but it has 0 KB. That's what I meant with no logs: an empty logfile. |
I am also on OpenSUSE (though 15.6, not Tumbleweed) and I can't connect anymore in My log files are also 0 bytes.
Here's the local vscode log, with some information obfuscated with "XXXXXX" characters.
Oddly, downgrading openssh on the server back down to something like 9.9p2-lp156.2.5 didn't fix the issue. |
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
setting[Optional] Diagnose with Copilot
I asked @remote-ssh but it did not help
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I COULD successfully SSH to the remote machine with the generated SSH command
Remote-SSH Log
Remote-SSH Log
Expected Behavior
In my Remote.SSH settings, use Exec Server was enabled (probably automatically as I read that this will be made the default for everyone). I wanted to connect to my remote host.
Actual Behavior
The connection failed, however the SSH connection itself seems to work just fine. Just the server couldn't be started. I also don't get any logs on the host in the .vscode-server directory on the host.
Steps To Reproduce
Anything else?
I executed the Copilot assistant chat the was offered in the error message. He told me several things to check which I followed and provided him with my findings. For instance, I didn't get any logs on the host, so Copilot concluded that the server died before being able to write some logs. He in the end concluded that my running opensuse-tumbleweed doesn't match the alpine related download path from the client logs. This could be related to using musl in Alpine vs. using glibc in openSUSE.
The text was updated successfully, but these errors were encountered: