Description: You are using the "Remote - SSH" VSCode extension to remotely log into c2s2-dev. It was working previously, but is no longer working.

Case 1:

What Happened?

VSCode installs a few files on the server to support logging in remotely. Occasionally, due to logging out weirdly or other things, these files can get to a state where VSCode can no longer log in (why? who knows )

How Do I Fix It?

Log into c2s2-dev using a Terminal. From here, we need to delete VSCode's server-side setup; this is stored in a hidden folder titled .vscode-server in your home directory. Delete this with the command:

rm -rf ~/.vscode-server

(Note: you may get that some files weren't deleted because they are "open or busy". Ensure that you have completely logged out of/quit VSCode, maybe wait a few minutes for lingering processes to finish, then try again)

From here, try logging on using VSCode again. This will force VSCode to re-install these files, which should therefore no longer be corrupted. If this doesn't work, see Case 2

Case 2:

What Happened?

As part of logging in, VSCode needs to create new files. It's possible that your memory limit on the server has been exceeded, meaning that VSCode cannot create the necessary files to log you in.

How Do I Fix It?

Logging in using a Terminal (which doesn't require files to be created to log in), follow the steps for resolving too much memory usage. Once that is complete, the files may still be in a unintended state; follow the fix for Case 1 to restore a new server-side installation.