-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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 Connection Issue with VS Code Using WSL on Windows #234515
Comments
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.95.3. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding! |
This has been going on long before I upgraded to the newest version. This is not the issue |
From the log snippet you've provided, it looks like the Remote - SSH extension is not using WSL? I see Windows paths.
That seems suspicious. I see you've been playing around with various settings. Could you include your entire log so we can see more about your environment? You might also want to take a look at some discussion in this issue, I think it will help: microsoft/vscode-remote-release#937 |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
I am experiencing issues connecting to a remote server (spirit.cin.ucsf.edu) via SSH in VS Code on Windows, using WSL as my primary environment. I am able to connect to the server without any problems through the WSL terminal directly, but when I attempt the connection through VS Code's Remote SSH extension, it fails with the following error:
The terminal process "C:\Windows\System32\cmd.exe /c (type "C:\Users\bellj\AppData\Local\Temp\vscode-linux-multi-line-command-spirit.cin.ucsf.edu-850316979.sh" | "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 61353 -F "/home/jackkrolik/.ssh/config" "spirit.cin.ucsf.edu" sh) & exit /b 0" terminated with exit code: 1.
Additionally, I receive extensive logs, including multiple errors about SSH binaries and configuration paths. Here is a portion of the log with key details:
[13:49:31.154] "remote.SSH.path": C:\Windows\System32\wsl.exe -e /home/jackkrolik/bin/ssh-wrapper.sh
[13:49:31.165] Setting up SSH remote "spirit.cin.ucsf.edu"
[13:49:32.329] Checking ssh with "C:\Windows\System32\wsl.exe -e /home/jackkrolik/bin/ssh-wrapper.sh -V"
[13:49:32.331] Got error from ssh: spawn C:\Windows\System32\wsl.exe -e /home/jackkrolik/bin/ssh-wrapper.sh ENOENT
[13:49:32.332] The specified path C:\Windows\System32\wsl.exe -e /home/jackkrolik/bin/ssh-wrapper.sh is not a valid SSH binary
Environment:
VS Code Version: 1.95.0
Remote-SSH Extension Version: 0.115.0
Operating System: Windows with WSL (Windows Subsystem for Linux)
WSL Distro: Ubuntu (using WSL as the terminal in VS Code)
Steps Taken:
Verified that SSH works directly in WSL.
Configured the SSH settings in VS Code's settings.json.
Attempted using both "remote.SSH.path": "wsl" and "remote.SSH.path": "C:\Windows\System32\OpenSSH\ssh.exe".
Ensured correct permissions for id_ed25519 and config files in .ssh directory.
Expected Outcome: To establish a stable SSH connection to the remote server (spirit.cin.ucsf.edu) within VS Code using WSL, as I can do directly through the WSL terminal.
Extension version: 0.115.0
VS Code version: Code 1.95.0 (912bb68, 2024-10-28T20:16:24.561Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 5.15.153.1-microsoft-standard-WSL2
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: