-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Comments
Is this on a remote server or your local instance? |
The same incident occurs to me, on a remote server, sometimes it connects quickly, others if it takes or does not. |
I'm not able to replicate this, might be a QoS issue with your ISP? |
I'm seeing this too with codercom/code-server@sha256:e614b21e92593483d379d6a6bac77f283f988ec59207cd224a8ad6272c0f7208 |
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 EDIT: I switched back to using Traefik proxy and I can no longer reproduce this issue 🤔 |
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. |
I think this might actually be traefik specific. It seems to work with nginx. |
I think it might be related to: traefik/traefik#5533 (comment) |
If this is still a problem, please feel free to reopen. |
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
The text was updated successfully, but these errors were encountered: