Skip to content

Connection gettting failed repeatedly #1161

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
PyExtreme opened this issue Nov 9, 2019 · 10 comments
Closed

Connection gettting failed repeatedly #1161

PyExtreme opened this issue Nov 9, 2019 · 10 comments
Labels
bug Something isn't working

Comments

@PyExtreme
Copy link

I am using the latest release of code-server released yesterday and the connection is failing again and again. Also, I have no internet issues and I have tested on different networks as well.

Attached is the screenshot which I am getting

Screenshot from 2019-11-09 13-51-34

@PyExtreme PyExtreme added the bug Something isn't working label Nov 9, 2019
@sr229
Copy link
Contributor

sr229 commented Nov 10, 2019

Is this on a remote server or your local instance?

@3l3n01
Copy link

3l3n01 commented Nov 13, 2019

The same incident occurs to me, on a remote server, sometimes it connects quickly, others if it takes or does not.

@sr229
Copy link
Contributor

sr229 commented Nov 13, 2019

I'm not able to replicate this, might be a QoS issue with your ISP?

@crossan007
Copy link

I'm seeing this too with codercom/code-server@sha256:e614b21e92593483d379d6a6bac77f283f988ec59207cd224a8ad6272c0f7208

@crossan007
Copy link

crossan007 commented Nov 14, 2019

Might be related to #1147, #442, #797

@crossan007
Copy link

crossan007 commented Nov 14, 2019

I was having this issue when my VSCode instance was behind a Traefik reverse-proxy instance. When I exposed the VSCode container's port 8080 directly, the websocket seemed to connect fine.

For full environment reference, I'm on Docker engine Server Version: 19.03.1, running on Windows Server 2019, with LCOW enabled (Linuxkit version 0.6+ , commit: ddb0fa509e6163bfbd71e9114ce8170b0a53c4fa), Traefik running with the nanoserver image, and VSCode running with the linux image via LCOW

EDIT: I switched back to using Traefik proxy and I can no longer reproduce this issue 🤔

@geiseri
Copy link
Contributor

geiseri commented Nov 27, 2019

I see this too with traefik, I am wondering if the websocket token is messed up. I can't tell though because it seems verbose in the latest build are broken.

@geiseri
Copy link
Contributor

geiseri commented Nov 28, 2019

I think this might actually be traefik specific. It seems to work with nginx.

@geiseri
Copy link
Contributor

geiseri commented Nov 28, 2019

I think it might be related to: traefik/traefik#5533 (comment)

@nhooyr
Copy link
Contributor

nhooyr commented Jan 29, 2020

If this is still a problem, please feel free to reopen.

@nhooyr nhooyr closed this as completed Jan 29, 2020
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