systemd unit won't persist

[hluker]

• Web Browser: Chrome 81.0.4044.129
• Local OS: Windows 10 10.0.18363 Build 18363
• Remote OS: Debian 10
• code-server --version: 3.3.0 52eecca
  Note: running behind Apache reverse-proxy

Last night, I re-built my development server and installed Code Server 3.3 using the guide provided (thanks!). Previously, I managed it via a systemd service which launched it on start-up and kept it running -- the guide now states to use 'systemctl --user restart code-server,' which works fine and launches it when the shell is open, but closes it when I close the shell. Is this behavior by design / is there any guidance for keeping it running?

[nhooyr]

If you run:

systemctl --user enable --now code-server

As mentioned in the guide, it should launch on startup.

restart is only for reloading from the config file.

If that doesn't work, lmk and I'll reopen this issue.

[hluker]

Same behavior with that command. Stays open for as long as the Terminal window is open.

[nhooyr]

Interesting, will try to reproduce.

[hluker]

Just as a note, I've upgraded to 3.3.1 6f13097 with same behavior observed.

[nhooyr]

Seems to work for me.

I created a Debian 10 VM on GCP and then installed code-server with the instructions from the guide. Then followed the guide to setup a self signed certificate and listen on 0.0.0.0:443. Verified I could connect to the instance's public IP and then rebooted.

Confirmed I could access code-server once the instance was up. Did not login into the VM until I verified I could access code-server.

[nhooyr]

Might be something different about your systemd setup.

We're also using a systemd service but it's a systemd user service.

It's at https://github.com/cdr/code-server/blob/aa872701481ad371f25a6cc7042ca1e55d05e782/ci/build/code-server.service and installed as part of the .deb.

What does systemctl get-default print?

[hluker]

Prints graphical.target

[nhooyr]

Seems right to me.

How about systemctl --user status code-server?

[hluker]

It's perplexing. It works as long as my user is logged in, and Nagios confirms that Node is running, but as soon as I exit the terminal, the application stops and Nagios says Node is not running.