marco44, this might be your fix:
sudo systemctl start netbird
sudo systemctl enable netbird
# or simply just
sudo systemctl enable --now netbird
If someone is getting context deadline exceeded error then do a proper uninstallation of netbird first following this comment: https://github.com/netbirdio/netbird/issues/1048#issuecomment-2440058691
sudo systemctl stop netbird
sudo systemctl disable netbird
sudo rm /usr/local/bin/netbird
sudo rm /usr/local/bin/netbird-ui
sudo rm /usr/bin/netbird
sudo rm /usr/bin/netbird-ui
sudo rm -rf /etc/netbird
sudo rm -rf /var/lib/netbird
sudo pacman -R netbird
sudo pacman -R netbird-bin-debug
and then install netbird fresh, it should work
Pinned Comments
shuurilabs commented on 2026-02-25 13:33 (UTC) (edited on 2026-02-26 15:07 (UTC) by shuurilabs)
Hi @tarball, I'm from the NetBird team.
This socket path mismatch has been fixed upstream. The CLI, UI, and SSH client now auto-discover the daemon socket when the default /var/run/netbird.sock doesn't exist - they scan /var/run/netbird/*.sock and use it if exactly one is found. So netbird@main.service will work out of the box without needing --daemon-addr or NB_DAEMON_ADDR.
The fix is in https://github.com/netbirdio/netbird/commit/ef82905526a5944e9aac96e04b8b7ee67d27c9b9. It's included as of v0.66.