Skip to content

Stuck on grey screen due to websocket error 500 #797

Closed

Description

@Burn-E99
  • 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.

Activity

  1. simonliii commented on Jun 23, 2019

    @simonliii

    I have the same issue.

  2. grant commented on Jun 28, 2019

    @grant

    Is there any support for alternatives (like long-polling / socket.io) rather than web sockets? Some environments don't support websockets.

  3. Mrgove10 commented on Aug 15, 2019

    @Mrgove10

    Same issue, even whit HTTPS

  4. deansheather commented on Aug 16, 2019

    @deansheather
    Collaborator

    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.

  5. Mrgove10 commented on Aug 16, 2019

    @Mrgove10

    i was not using a reverse proxy in my case

  6. deansheather commented on Aug 19, 2019

    @deansheather
    Collaborator

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

  7. code-asher commented on Nov 1, 2019

    @code-asher
    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions