Closed soul-codes closed 4 years ago
I can confirm that a fresh install on a completely newly spun server on DigitalOcean reproduces this issue.
For a completely mysterious reason, it "suddenly works" again, so I guess this could have been seen as an Act of God or perhaps a cloud provider's temporary network issue of some kind. In any case, I am no longer personally affected by this issue, but I'll leave it open in case the logs above hint at any genuine bug.
It might not have been a network issue since it looks like only the extension host is trying to reconnect while the other socket appears stable. It's possible the extension host was crashing or exiting for some reason. There might be more information that explains why in VS Code's logs which are in ~/.local/share/code-server/logs/[date]
by default.
I'll close for now since it's working for you and I don't see anything actionable in the logs, but if it happens again or if you still have those logs definitely feel free to post them here!
As of today, my code-server spontaneously "stopped working" in several areas -- TypeScript language features aren't working, the integrated terminal doesn't start, and none of the extensions work. Scanning through the front and backend logs makes me think that some communication issue is happening that is critical to the whole application.
Sorry if this turns out to be just some misconfiguration but as "nothing has changed" between last night when it was working properly and this morning (including configuration), I wonder if this might be a bug.
Restarting the server doesn't help. There is no difference between running it as a service with
systemctl
or directly executingcode-server
.Reboot my host machine also doesn't help.
code-server --version
: 3.4.1 48f7c2724827e526eeaa6c2c151c520f48a61259Logs and configs follow.
<<secret:my_host>>
represents a valid domain name like xyz.com that is my private development domain.Config
Code-server stdout log
Chrome log