Skip to content
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

ssh disconnections #192647

Closed
jjarokergc opened this issue Sep 9, 2023 · 13 comments
Closed

ssh disconnections #192647

jjarokergc opened this issue Sep 9, 2023 · 13 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@jjarokergc
Copy link

jjarokergc commented Sep 9, 2023

Type: Bug

Latest version was installed last night via snap. Now I cannot connect to any remote host via the Remote Development module. SSH connects successfully, according to sshd logs on the remote. But VScode disconnects from the remote. There are no error message on the remote sshd log that would indicate any reason for the disconnection.

This happens on all 3 remote hosts that I typically develop on. Before the snap update, these connections worked fine.

I needed to revert to the previous version to regain remote development:

jjaroker@puma:~$ snap list code --all
Name  Version   Rev  Tracking       Publisher  Notes
code  6c3e3dba  137  latest/stable  vscode✓    classic
code  8b617bd0  138  latest/stable  vscode✓    disabled,classic

VS Code version: Code 1.82.0 (8b617bd, 2023-09-06T22:07:18.759Z)
OS version: Linux x64 5.15.0-83-generic snap
Modes:
Connection to 'SSH: puppet.staging' could not be established Canceled

System Info
Item Value
CPUs Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz (32 x 1200)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
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
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) 1, 1, 0
Memory (System) 125.79GB (122.92GB free)
Process Argv --no-sandbox --force-user-env --unity-launch
Screen Reader no
VM 0%
DESKTOP_SESSION plasma
XDG_CURRENT_DESKTOP KDE
XDG_SESSION_DESKTOP KDE
XDG_SESSION_TYPE x11

Connection to 'SSH: puppet.staging' could not be established Canceled

Extensions: none
@binnn6
Copy link

binnn6 commented Sep 9, 2023

Same problem, fixed by switch "Remote - SSH" extension to Pre-Release Version.

@shangbinbin
Copy link

Same problem, fixed by switch "Remote - SSH" extension to Pre-Release Version.

👍it works for me.

@mcognetta
Copy link

I had a similar problem and the ssh connection would hang with the message

Failed to set up socket for dynamic port forward to remote port ...:

I was able to ssh successfully from my terminal, but not from VSCode. I rolled back the remote ssh extension to a few different versions, but eventually that worked.

I first tried the prelease version, but that didn't work. I had to roll it back two versions before it worked.

@connor4312
Copy link
Member

I would be grateful if you could grab the "Remote - SSH" log from the "Output" tab in the bottom panel of VS Code when you get into this broken state. Note that we've turned off the problematic functionality in stable for the moment, but it can be turned back on via the "remote.SSH.useExecServer": true setting. Please turn that on for a few minutes and see if you can still get the failure. Thanks!

@connor4312 connor4312 added the info-needed Issue requires more information from poster label Sep 11, 2023
@webjema
Copy link

webjema commented Sep 12, 2023

I have the same issue. Please find logs attached.
Issue is fixed switching to pre-release extension.

VScode_SSH_Log_Level.txt

@connor4312
Copy link
Member

@webjema your issue is the same as microsoft/vscode-remote-release#8942 (comment) which will be fixed when you update to the latest extension version (0.106.3)

@jjarokergc
Copy link
Author

Hello @connor4312

I attempted to get the additional information you requested, but there is no output generated.

Here is my environment:

jjaroker@puma:~$ snap list code --all
Name  Version   Rev  Tracking       Publisher  Notes
code  6c3e3dba  137  latest/stable  vscode✓    disabled,classic
code  65091741  139  latest/stable  vscode✓    classic

Enabling the option "Remote.SSH:Use ExecServer" and then making a remote connection resulted in several loops of "Downloading VS Code..." and finally an error "Could not fetch remote environment".

Here is a screenshot of what I observe. The Output tab is blank.

image

@connor4312
Copy link
Member

Hi, you'll want to use the select box in the upper right side of the bottom panel and switch to "Remote - SSH". That should have the output. Thanks!

@jjarokergc
Copy link
Author

Sorry about that.

Attached are files from the ssh remote output and the error messages that appear on vscode console.

sshremote.log
vscode-app-1694631240522.log
vscode-app-1694631415189.log

connor4312 added a commit that referenced this issue Sep 21, 2023
connor4312 added a commit that referenced this issue Sep 21, 2023
connor4312 added a commit that referenced this issue Sep 21, 2023
@corford
Copy link

corford commented Oct 5, 2023

Enabling "remote.SSH.useExecServer": true fixed it for me (before I was getting "Error opening exec server" when trying to launch a dev container via a remote SSH workspace

@ciricc
Copy link

ciricc commented Oct 5, 2023

Enabling "remote.SSH.useExecServer": true fixed it for me (before I was getting "Error opening exec server" when trying to launch a dev container via a remote SSH workspace

Me too. Helped to fix reopening in the dev container command execution.

@connor4312
Copy link
Member

THat is tracked in microsoft/vscode-remote-release#9064, release will be out shortly

@VSCodeTriageBot
Copy link
Collaborator

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!

@VSCodeTriageBot VSCodeTriageBot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 13, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Nov 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests