-
Notifications
You must be signed in to change notification settings - Fork 6k
Stuck on grey screen due to websocket error 500 #797
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have the same issue. |
Is there any support for alternatives (like long-polling / socket.io) rather than web sockets? Some environments don't support websockets. |
Same issue, even whit HTTPS |
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. |
i was not using a reverse proxy in my case |
@Mrgove10 Does anything appear in the code-server log or browser log that could be helpful? |
If anyone still experiences this on v2 lemme know. |
code-server
version: 1.1156-vsc1.33.1Description
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
Let me know if more details are needed, such as what my configs are currently set at.
The text was updated successfully, but these errors were encountered: