Florian Ritterhoff

So I might be wrong but the only location where upstream vs code prepends the PATH variable with the remote-cli folder is here: https://github.com/microsoft/vscode/blob/619ab6d1ba7eef9ad418456a5fe5c7805f01a7ab/src/vs/server/node/extensionHostConnection.ts#L53-L59 This is also used to spawn...

My pretty simple idea would be to check inside the code-server script it's location. So in case of being inside the `remote-cli` folder instead of the `bin` it maybe would...

I'm currently trying what happens if I simply remove the code-server script located in `remote-cli` folder.

 So removing the `code-server` script inside the `remote-cli` folder at least works in my case fine... Not sure if there are some negative side-effects I did not see in...

> I think the ideal solution is going to be to fix upstream's `code-server` script so that it can find Node. This means invocations on the integrated terminal will use...

I've got a quite similar bug. Accessing the code server (behind a https reverseproxy) from MS Edge and Chrome works without any noticeable problems, opening the same setup in a...

 I've blurred out the internal fqdn...

In comparison using MS Edge: 

Hi @jsjoeio, I'm using the latest docker image (`codercom/code-server:latest`). That is running a code-server 3.12.0  Running in an incognitor window: 

@code-asher Yep, the service worker is missing in the private window. I'm using code-server 3.12.0 and I'm using the recent Firefox 93.0 (64 bit)