You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Anything between here and the comment below will become the contents of the drop-in file
[Service]
ExecStart=
ExecStart=/usr/bin/code-server /my/super/path
User=superuser
Group=superuser
### Edits below this comment will be discarded
### /usr/lib/systemd/system/[email protected]
# [Unit]
# Description=code-server
# After=network.target
#
# [Service]
# Type=exec
# ExecStart=/usr/bin/code-server
# Restart=always
# User=%i
#
# [Install]
# WantedBy=default.target
Are you sure the socket is deleted? That socket should be unrelated to the web socket in the console messages (the three hour one).
The timeout is one specified by VS Code, not us, but we could patch it if we really need to. From what I understand, it is really just meant to reconnect when there is a blip in the network. Reloading the page should result in a new connection, but is that not working either?
Is there an existing issue for this?
OS/Web Information
code-server --version
: 4.95.2Steps to Reproduce
logs below:
You will never reconnect to code-server because the socket file is delete.
Expected
Never delete the socket file unless code-server is stopped
Actual
It deleted!
Logs
Screenshot/Video
No response
Does this bug reproduce in native VS Code?
This cannot be tested in native VS Code
Does this bug reproduce in GitHub Codespaces?
I did not test GitHub Codespaces
Are you accessing code-server over a secure context?
Notes
my nginx config:
And systemctl edit code-server.service:
And the config.yaml
The text was updated successfully, but these errors were encountered: