code-server | Non-root Docker image running Debian and code-server | Continuous Deployment library

The issue seems to be due to proxy configuration in the VSCode settings. Removing it has resolved the delay.

It sounds like the locks are getting stuck even when the server closes. So on reconnect vscode won't start a new server (because of the lock) but can't connect to the "existing" server because it's already closed

That's where this first option "remote.SSH.useFlock" comes in. It controls whether vs code uses the flock system call or ln to lock files. Setting this will clean up most issues you could have with mounts that might have issues support flock.

The second option "remote.SSH.lockfilesInTmp" re-locates the lock files completely (moving them to tmp) because some mounts (like SSH) may have issues even with the ln approach to locking. The downside here is that this moves lock files way from the actual install. So if there's a risk that install may be shared (NFS, shared home, link to shared area, etc.) then vscode may "miss" locks.

If "remote.SSH.useFlock": false works for you I would keep that.

If you need to use "remote.SSH.lockfilesInTmp": true take care to avoid running multiple servers out of the same install.

You would need to get the tag using get latest release API:

Coincidentally, I had this problem with my VSCode just today as well! For me, it just stopped working today all of a sudden (may have something to do with the latest VScode update). The problem is that VSCode can no longer find your ssh program, which it was previously able to do.

1. Go to your Remote-SSH preferences (cmd + , and search for remote-ssh).
2. Find the field labeled Remote.SSH: Path. Right now it's probably blank for you because VSCode used to find the executable by itself.
3. Input the absolute path to your ssh executable. If you are unsure of the path, you can run which ssh in your terminal and copy the path it prints out.
4. Save your settings, and retry the ssh. Worked for me!

This works for me with code-server 3.9.0 and manually installing the extension via VSIX. (I built the extension from GitHub)

If you want to request this extension in the code-server marketplace, you can file an issue. code-server will soon be integrated with the open-vsx marketplace, so it could be supported there: https://github.com/cdr/code-server/pull/2659

picture: code-server with Haskell

I solved this problem by downgrading the version of the Python extension to v2021.1.502429796. Hopefully this gets fixed at some point.

There is an issue raised on the official GitHub repo regarding this, you can follow up there

https://github.com/microsoft/vscode-eslint/issues/1156

The error message indicates that the .deb is designed to use systemd, which WSL doesn't support (without a lot of extra effort).

However, it appears that code-server supports a "standalone" (non-package) based installation. See this section of the install doc for details.

There are a few reports of a similar issue in the microsoft/vscode-remote-release project which implements for VSCode this feature.

For instance, issue 4008

The remote OS I am connecting to is a RHEL 7 Linux machine.

I tried fiddling with iptables and ports for the wget request to no avail.
It hangs for a little while at the wget step, and ultimately fails to connect. I tried tweaking just about every SSH setting in the remote.

The only other thing I noticed that might be related was with the Ports Available text at the bottom of the screen. It never reads anything other than 0 during the connection process. When I'm properly connected, it says 1 Port Available.

However, I did find a successful workaround: I rolled back the Remote SSH extension to 0.55.0 and it worked like a charm again.

So try and downgrade the Remote SSH extension, to see if it works.