Skip to content

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

Closed
Burn-E99 opened this issue Jun 20, 2019 · 7 comments
Closed

Stuck on grey screen due to websocket error 500 #797

Burn-E99 opened this issue Jun 20, 2019 · 7 comments
Labels
bug Something isn't working

Comments

@Burn-E99
Copy link

  • code-server version: 1.1156-vsc1.33.1
  • OS Version: Ubuntu Server 16.04 on private VPS

Description

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

  1. Download the binary and run it on server with --allow-http
  2. Configure Apache according to docs
  3. Attempt to access via chrome
  4. 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.

@Burn-E99 Burn-E99 added the bug Something isn't working label Jun 20, 2019
@simonliii
Copy link

I have the same issue.

@grant
Copy link

grant commented 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
Copy link

Same issue, even whit HTTPS

@deansheather
Copy link
Member

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
Copy link

i was not using a reverse proxy in my case

@deansheather
Copy link
Member

@Mrgove10 Does anything appear in the code-server log or browser log that could be helpful?

@code-asher
Copy link
Member

If anyone still experiences this on v2 lemme know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants