CODEWITHSUNDEEP
visual-studio-codessh
citelao
citelao

Reputation: 6076

VS Code SSH keeps dropping connections, but I can SSH just fine

I set up SSH on a remote machine & a local machine, with the intent of using VS Code SSH. I can connect to my remote with ssh in the command line, but VS Code keeps dropping connections after successfully connecting with something like ssh child died, shutting down.

Why can I connect via CLI SSH, but not VS Code? How do I fix this?

Background

How do I fix this, so I can connect in VS Code?

Upvotes: 4

Views: 4731

Answers (3)

mrbarletta
mrbarletta

Reputation: 922

I had a different issue, we use Cloudflare SSH for infrastructure, like a tunnel, and seems this SSH tunneling was affecting VsCode, so I switched back to direct SSH connection and it worked.

too bad

Upvotes: 0

Sara
Sara

Reputation: 45

This has happened to me with new updates of VS Code. What fixes the problem for me usually is:

  1. deleting vs code from the server:

    rm -rf ~/.vscode-server
    rm -rf ~/.vscode

  2. Switching to a pre-release version of vs code ssh.

Once you ssh back into the remote server from vs code, vs code will reinstall and reconfigure itself.

Upvotes: 0

citelao
citelao

Reputation: 6076

Solution

Disable Remote.SSH: Use Local Server (set remote.SSH.useLocalServer to false):

Use Local Server

Per Rob Lourens in this GitHub issue:

You are hitting a bug with some versions of the windows ssh server :/

More information

Relevant logs from the issue (I couldn't get my own logs after fixing the issue):

[16:11:07.635] stderr> Authenticated to 127.0.0.1 ([127.0.0.1]:22).
[16:11:10.183] stderr> client_loop: send disconnect: Connection reset by peer
[16:11:10.244] > local-server-1> ssh child died, shutting down
[16:11:10.368] Local server exit: 0

// ...

client_loop: send disconnect: Connection reset by peer
local-server-1> ssh child died, shutting down

[16:11:10.370] Failed to parse remote port from server output
[16:11:10.374] Resolver error: Error: 
    at Function.Create (c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:585789)
    at Object.t.handleInstallOutput (c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:584441)
    at Object.e [as tryInstallWithLocalServer] (c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:624908)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:643945
    at async Object.t.withShowDetailsEvent (c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:647692)
    at async c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:623380
    at async b (c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:619886)
    at async Object.t.resolveWithLocalServer (c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:622995)
    at async Object.t.resolve (c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:645302)
    at async c:\Users\alros\.vscode-insiders\extensions\ms-vscode-remote.remote-ssh-0.79.2022040715\out\extension.js:1:722235
[16:11:10.380] ------

Upvotes: 3

Related Questions