Cannot reconnect. Please reload the window. (nginx as a reverse proxy)

[nathanchu]

I've just installed code-server on a DO droplet, but I am having some issues. I accessed it at http://[my-ip]:8080, and it seems to work fine. However, when I set up nginx and used this as a reverse proxy to port 8080, it only works for around a minute before I get a "Cannot reconnect. Please reload the window." error. I can reload it and it works fine, but it usually will stop working after a minute. I installed code-server via the script, with Node.js version 12.18.4 LTS. I don't know if this helps, but I have 1gb RAM and 1vCPU, so it may be an issue with the droplet being underpowered. I don't know if this helps either, but code-server got killed recently because of an OOME. If anyone could help, I'd really appreciate it.

[nathanchu]

I solved my own problem! I created a new droplet and it worked perfectly 🤷‍♂️. I guess I broke the config files.

[nathanchu]

Never mind, it seems that new VMs work better than older ones. I haven't edited the log files, but code-server pops up with "Cannot reconnect. Please reload the window." especially when opening large log files, and when opening the terminal. As a side note, this only happens when using nginx so it could either be the ssl cert or ngnix (I haven't tested nginx without ssl yet).

[code-asher]

Yup that works for me. The VS Code logs should be clean but I think you're right that code-server's logs include the password if you're in debug mode which we should fix.

Although, thinking more about this problem it may be that the server logs won't help (the browser ones might). I think it might be that the websockets aren't connecting at all. If the page doesn't have a green lock that means the browser thinks the certificate is invalid and I think Chrome will not allow websocket connections with invalid certs.

That's why I was thinking that using http might work (since there would be no invalid certificates for Chrome to complain about) but if that's just showing a blank page while https doesn't then it seems like that might be an nginx configuration issue.

[nathanchu]

Yup that works for me. The VS Code logs should be clean but I think you're right that code-server's logs include the password if you're in debug mode which we should fix.

Although, thinking more about this problem it may be that the server logs won't help (the browser ones might). I think it might be that the websockets aren't connecting at all. If the page doesn't have a green lock that means the browser thinks the certificate is invalid and I think Chrome will not allow websocket connections with invalid certs.

That's why I was thinking that using http might work (since there would be no invalid certificates for Chrome to complain about) but if that's just showing a blank page while https doesn't then it seems like that might be an nginx configuration issue.

It's actually a gray lock. I hope that's okay. The cert still appears trusted at ssllabs, and in my browser.

[code-asher]

I think as long as the browser logs don't have any errors about it you're good. For example here's what mine says when I load a certificate it doesn't like:

vscode.js:993 WebSocket connection to 'wss://8080.dev.localhost:44983/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
Uncaught (in promise) DOMException: Failed to register a ServiceWorker for scope ('https://8080.dev.localhost/') with script ('https://8080.dev.localhost/static/development/src/code-server/dist/serviceWorker.js'): An SSL certificate error occurred when fetching the script.

[nathanchu]

I think as long as the browser logs don't have any errors about it you're good. For example here's what mine says when I load a certificate it doesn't like:

vscode.js:993 WebSocket connection to 'wss://8080.dev.localhost:44983/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
Uncaught (in promise) DOMException: Failed to register a ServiceWorker for scope ('https://8080.dev.localhost/') with script ('https://8080.dev.localhost/static/development/src/code-server/dist/serviceWorker.js'): An SSL certificate error occurred when fetching the script.

I don't see those. I just scanned through the logs again and it is, in fact, getting killed by OOM! Your system requirements say that 1gb ram should be fine and that's what I have though. I'm going to test this locally (with a vm, 2gb ram and 2vCPU to make sure OOM won't be a problem) and give myself a certificate signed by my own private CA (to better emulate let's encrypt), and trust that root certificate in chrome. I'll let you know if I still receive the error of cannot reconnect. I have seen the following error when running it locally though, so if it helps:

(node:31) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [ChildProcess]. Use emitter.setMaxListeners() to increase limit

(node:31) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [ChildProcess]. Use emitter.setMaxListeners() to increase limit

[code-asher]

Ahh I'm sorry about that. We pull the 1GB requirement from VS Code but it's possible code-server has a higher overhead or maybe there is a memory leak like noted in those logs. I'll investigate.