starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[docs/server,sqlite] Locked database, likely due to SystemD unit #442

New Issue
Closed
opened 2025-12-29 01:29:26 +01:00 by adam · 1 comment
adam commented 2025-12-29 01:29:26 +01:00
Owner
Copy Link

Originally created by @IngwiePhoenix on GitHub (Mar 20, 2023).

Bug description

After following the documentation for creating a Headscale instance on Linux, I used the recommended method of running it in the background - https://github.com/juanfont/headscale/blob/main/docs/running-headscale-linux.md#running-headscale-in-the-background-with-systemd - and successfuly saw my instance started. I did only change the permissions of /etc/headscale recursively to the headscale:headscale user.

Problem is though, I can not create a new user now.

root@drachennetz:/var/lib/headscale# ls -la .
total 12
drwxr-xr-x  2 headscale headscale 4096 Mar 20 14:06 .
drwxr-xr-x 55 root      root      4096 Mar 20 12:44 ..
-rw-------  1 headscale headscale  120 Mar 20 14:06 .bash_history
-rw-r--r--  1 headscale headscale    0 Mar 20 12:46 db.sqlite
root@drachennetz:/etc/headscale# ls -la .
total 88
drwxr-xr-x   2 headscale headscale  4096 Mar 20 13:55 .
drwxr-xr-x 116 root      root      12288 Mar 20 13:06 ..
-rw-r--r--   1 headscale headscale 11554 Mar 20 13:53 config.yaml
-rw-r--r--   1 headscale headscale 49152 Mar 20 13:50 db.sqlite
-rw-------   1 headscale headscale    72 Mar 20 13:08 noise_private.key
-rw-------   1 headscale headscale    72 Mar 20 13:08 private.key

I copied the systemd unit as-is.

[Unit]
Description=headscale controller
After=syslog.target
After=network.target

[Service]
Type=simple
User=headscale
Group=headscale
ExecStart=/usr/local/bin/headscale serve
Restart=always
RestartSec=5

# Optional security enhancements
NoNewPrivileges=yes
PrivateTmp=yes
ProtectSystem=strict
ProtectHome=yes
WorkingDirectory=/var/lib/headscale
ReadWritePaths=/var/lib/headscale /var/run/headscale
AmbientCapabilities=CAP_NET_BIND_SERVICE
RuntimeDirectory=headscale

[Install]
WantedBy=multi-user.target

To Reproduce

Follow the instructions for Linux top to bottom.

Context info

root@drachennetz:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
root@drachennetz:~# headscale version
v0.20.0

My use-case is very small: three maschines and two users. I want to allow my friend in Berlin to access my SMB share on my NAS, as well as myself on my laptop when away. :)

Originally created by @IngwiePhoenix on GitHub (Mar 20, 2023). **Bug description** After following the documentation for creating a Headscale instance on Linux, I used the recommended method of running it in the background - https://github.com/juanfont/headscale/blob/main/docs/running-headscale-linux.md#running-headscale-in-the-background-with-systemd - and successfuly saw my instance started. I did only change the permissions of `/etc/headscale` recursively to the `headscale:headscale` user. Problem is though, I can not create a new user now. ``` root@drachennetz:/var/lib/headscale# ls -la . total 12 drwxr-xr-x 2 headscale headscale 4096 Mar 20 14:06 . drwxr-xr-x 55 root root 4096 Mar 20 12:44 .. -rw------- 1 headscale headscale 120 Mar 20 14:06 .bash_history -rw-r--r-- 1 headscale headscale 0 Mar 20 12:46 db.sqlite root@drachennetz:/etc/headscale# ls -la . total 88 drwxr-xr-x 2 headscale headscale 4096 Mar 20 13:55 . drwxr-xr-x 116 root root 12288 Mar 20 13:06 .. -rw-r--r-- 1 headscale headscale 11554 Mar 20 13:53 config.yaml -rw-r--r-- 1 headscale headscale 49152 Mar 20 13:50 db.sqlite -rw------- 1 headscale headscale 72 Mar 20 13:08 noise_private.key -rw------- 1 headscale headscale 72 Mar 20 13:08 private.key ``` I copied the systemd unit as-is. ```systemd [Unit] Description=headscale controller After=syslog.target After=network.target [Service] Type=simple User=headscale Group=headscale ExecStart=/usr/local/bin/headscale serve Restart=always RestartSec=5 # Optional security enhancements NoNewPrivileges=yes PrivateTmp=yes ProtectSystem=strict ProtectHome=yes WorkingDirectory=/var/lib/headscale ReadWritePaths=/var/lib/headscale /var/run/headscale AmbientCapabilities=CAP_NET_BIND_SERVICE RuntimeDirectory=headscale [Install] WantedBy=multi-user.target ``` **To Reproduce** Follow the instructions for Linux top to bottom. **Context info** ``` root@drachennetz:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04.6 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.6 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal root@drachennetz:~# headscale version v0.20.0 ``` My use-case is very small: three maschines and two users. I want to allow my friend in Berlin to access my SMB share on my NAS, as well as myself on my laptop when away. :)
adam added the bug label 2025-12-29 01:29:26 +01:00
adam closed this issue 2025-12-29 01:29:26 +01:00
adam commented 2025-12-29 01:29:27 +01:00
Author
Owner
Copy Link

@IngwiePhoenix commented on GitHub (Mar 20, 2023):

I later realized that my DB was set to a relative path. Might want to address that in the guide as well - it does mention changing the socket path, but not the DB. :)

@IngwiePhoenix commented on GitHub (Mar 20, 2023): I later realized that my DB was set to a relative path. Might want to address that in the guide as well - it does mention changing the socket path, but not the DB. :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#442
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?