You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Stuck on grey screen due to websocket error 500 #797
Installed code-server a couple days ago and finally went around to getting the reverse proxy working so I can use it on a semi-restricted network (network blocks direct IP:port access). Followed the docs for setting one up using Apache, and it somewhat works. The login page shows up and is usable, but once logged in, it sits on a grey screen repeatedly spitting out websocket connection to 'ws://coder.mydomain.com' failed: Error during websocket handshake: Unexpected response code: 500. Direct access over IP:port works, but the Apache reverse proxy only seems to partially work.
This happens in latest version of desktop chrome.
Steps to Reproduce
Download the binary and run it on server with --allow-http
Configure Apache according to docs
Attempt to access via chrome
Enter password and your at a grey screen, constantly getting a websocket 500.
Let me know if more details are needed, such as what my configs are currently set at.
This is likely caused by a misconfigured reverse proxy. I'm reviewing the reverse proxy documentation and rewriting parts that aren't clear or incorrect with the current version right now.
Activity
simonliii commentedon Jun 23, 2019
I have the same issue.
grant commentedon Jun 28, 2019
Is there any support for alternatives (like long-polling / socket.io) rather than web sockets? Some environments don't support websockets.
Mrgove10 commentedon Aug 15, 2019
Same issue, even whit HTTPS
deansheather commentedon Aug 16, 2019
This is likely caused by a misconfigured reverse proxy. I'm reviewing the reverse proxy documentation and rewriting parts that aren't clear or incorrect with the current version right now.
Mrgove10 commentedon Aug 16, 2019
i was not using a reverse proxy in my case
deansheather commentedon Aug 19, 2019
@Mrgove10 Does anything appear in the code-server log or browser log that could be helpful?
code-asher commentedon Nov 1, 2019
If anyone still experiences this on v2 lemme know.