-
Notifications
You must be signed in to change notification settings - Fork 5.9k
"Could not reconnect" #2144
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
Could you grab the extension host and code-server logs? https://github.com/cdr/code-server/blob/v3.5.0/doc/FAQ.md#how-do-i-debug-issues-with-code-server |
Just as an FYI. I got this same pop up lot with the current version of code server and so reverted to the previous release. |
Interesting, there have been a number of reports now that 3.5.0 has this problem while 3.4.1 doesn't. I'll take a look at the differences, maybe something will stand out. |
@code-asher You are not able to reproduce I assume? If you don't see anything I'll try to recreate a docker container that would demonstrate it happening regularly. Let me know. |
Correct, I haven't been able to reproduce yet. If you can recreate it in a Docker container that would be helpful! |
Having a hard time pinning this down but I think it happens predominately when I'm working with python files so I think there might be an interaction there. Packages used are the latest from market place. I did create a docker file and the easiest way to launch code server from that container is to run the script in the attached zip file. The docker image is vnijs/rsm-msba-cdr and Code Server is started from JypyterLab on port 8989. Python libraries used: VisualStudioExptTeam.vscodeintellicode-1.2.10.vsix The other packages used shown below. CoenraadS.bracket-pair-colorizer-2-0.2.0.vsix |
Same issue here. Happens as soon as the window is loaded. Will probably revert back to 3.5.0 for now. |
Hi, @hanneshayashi . I had the same issue after upgrade to 3.6.0. Resolved it after rebooting my machine. |
Same Issue for me on both 3.5.0 & 3.6.0. And it seems that if I use a global VPN, then I can reconnect again. If turn off the VPN, I can only connect for the first time after rebooting, and cannot reconnect after refreshing the page. I really need the bug fix in v3.6.0, so that I have to add my code-server host ip into my PAC file and let the signal go around the world and finally reach out to my server in the same city. :( Another finding: I only need VPN to initialize the connecting. Then I can turn the VPN off and hit "reconnect". |
Well, what do you know, a reboot actually fixed it. Thanks! I don't usually reboot my dev machine after just a software update and I don't really understand why a reboot would be necessary, but you can't argue with results! |
The messages/issue is hard to pin down and I don't see anything in "code-server --log trace". It happens sometimes after I install an extension that needs a reload to start working. I can only tell that the error is about to happen the fact that BracketPairColorizer (version 1 because version 2 doesn't work with 3.5 or 3.6) doesn't kick in right away. https://marketplace.visualstudio.com/items?itemName=CoenraadS.bracket-pair-colorizer |
Just tried out 3.6.1. "Cannot reconnect" seems to happen pretty much any time I click an icon in the left navigation bar now. Something about a "handshake timeout" (see below). The docker container I use is
|
@code-asher FYI I have been playing around with 3.6.2 for a few hours now in a docker container. I haven't seen any "reconnect" issues! Also, all extensions I have tried (incl python) seem to work! Well, except for Bracket-pair-colorizer-2 that is :) |
Yes!! I'm relieved to hear that. Thank you for testing it out.
Hopefully I'll have time to fix the bracket colorizer plugin soon
(most likely it will be next week).
|
Closing for now, if anyone sees more connection failures please let me know. Will use #2197 to track the bracket plugin issue. |
code-server --version
: 3.4.1 / 3.5.0"Could not reconnect" error, I reinstalled code-server many times and I could not find solution for this error.


It seems to disconnect at the same point the terminal would have been loaded.
The text was updated successfully, but these errors were encountered: