40

I just updated VSCode Remote Insider and I can't connect to my host through VSCode anymore.

I tried to uninstall my local VSCode Insider and restart it, but it didn't help. Then, I removed the .vscode-remote-insider directory on my host. However, VSCode remote can't re-install a remote service as the old one is still running. The following is the output from my local VSCode client.

remote-ssh@0.44.0
win32 x64
SSH Resolver called for "ssh-remote", attempt 1
SSH Resolver called for host: 121
Setting up SSH remote "121"
Using commit id "c089daa858f34631f5f827ff8a0313bf1e2ded6d" and quality "insider" for server
Testing ssh with ssh -V
ssh exited with code: 0
Got stderr from ssh: OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4
Install and start server if needed
> 
> Installing to /home/***/.vscode-server-insiders/bin/c089daa858f34631f5f827ff8a0313bf1e2ded6d...
> 
> Downloading with wget
> 
> Download complete
> 
> Found running server...
> 
> *
> * Reminder: You may only use this software with Visual Studio family products,
> 
> * as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
> *
> 
> Server did not start successfully. Full server log >>>
> <<< End of server log
> cat: /home/***/.vscode-server-insiders/.c089daa858f34631f5f827ff8a0313bf1e2ded6d.log: No such file or directory
> cat: /home/***/.vscode-server-insiders/.c089daa858f34631f5f827ff8a0313bf1e2ded6d.log: No such file or directory
> cat: /home/***/.vscode-server-insiders/.c089daa858f34631f5f827ff8a0313bf1e2ded6d.log: No such file or directory
> 
"install" terminal command done
Received install output: cat: /home/***/.vscode-server-insiders/.c089daa858f34631f5f827ff8a0313bf1e2ded6d.log: No such file or directory
Failed to parse remote port from server output: cat: /home/shawnguo/.vscode-server-insiders/.c089daa858f34631f5f827ff8a0313bf1e2ded6d.log: No such file or directory

The biggest trouble is that I can't kill the processes of VSCode on my host as they could always produce a new process when the old one is killed.

Melebius
  • 6,183
  • 4
  • 39
  • 52
Shawn Guo
  • 513
  • 1
  • 4
  • 7
  • @Melebius killing a process is a generic OS thing, and not specific to programming – Mark Rotteveel Apr 18 '23 at 08:50
  • @MarkRotteveel Yes but VS Code Server is still somewhat specific: It’s a [set of processes](https://stackoverflow.com/a/60420090/711006) and the client offers [an integrated way to kill the server](https://stackoverflow.com/a/57494961/711006). – Melebius Apr 19 '23 at 08:20

4 Answers4

103

Try to kill vs code-remote host through the command after pressing ctrl + shift + p and enter

Remote-SSH: kill VS Code Server on Host...

Then choose your host

  • Also if there are new never-existed-before problems with remote VS Code like entering SSH password many times but without success, after killing the process as mentioned above, delete the `.vscode` folder in the home directory of the remote. – Sorush Jul 28 '22 at 13:22
21

It works for me just killing the process called "node":

 killall node

Of course, it's not a perfect solution, just a work around.

Antonio Martino
  • 267
  • 2
  • 3
2

ps uxa | grep .vscode-server | awk '{print $2}' | xargs kill -9

inselberg
  • 549
  • 3
  • 13
  • 27
2

pkill -9 vscode-server worked for me.

Ibrahim Hadzic
  • 101
  • 1
  • 3