...
This solution option could introduce other problems to work through, so do this as a last resort. If any files were open and modified (but not saved yet) using Remote-SSH, via regular terminal NOT VS Code, deleting the vscode-server's files manually could cause cached files open in the editor to be lost. That can't be predicted ahead of time, so just be aware.
First, back up the contents of ~/.vscode-server where ~ is the path to your home directory, before continuing by copying the directory such as "cp :
| Code Block | ||||
|---|---|---|---|---|
| ||||
cp -pr $HOME/.vscode-server $HOME/.vscode-server-backup |
...
if you're worried about vitally important cached information being lost, the files may be retrievable manually. The next step will delete the cache entirely and irretrievably.
The server process binary and its associated files and cache usually are in the $HOME/.vscode-server/bin directory. Get rid of all the vscode-server files by running the following command on the remote server from an ordinary SSH terminal window:
| Code Block | ||||
|---|---|---|---|---|
| ||||
rm -rf $HOME/.vscode-server |
The next time the VSCode client is used to remotely connect, it should re-install the vscode-server files and provide a working session.
...