Describe the problem
Using the VPS provider’s control panel, I took a backup of the VPS when Netbird was properly functioning. I did this so that I could restore the image if things went wrong when I attempted to add other services onto the server. After restoring the image, I get 404 and intermittent 502 errors when attempting to access the Netbird webadmin.
However, all clients can connect and seem to be functioning as they should.
To Reproduce
Steps to reproduce the behavior:
- Go to ‘netbird.example.com’
- See nothing but 404 or 502 error
Expected behavior
Be prompted to login to the Netbird webadmin.
Are you using NetBird Cloud?
Self-hosted
NetBird version
v0.79.0
Is any other VPN software installed?
No
Debug output
To help us resolve the problem, please attach the following anonymized status output
netbird status -dA
Peers detail:
Events:
[INFO] SYSTEM (31b4f8b3-e7a5-4615-a520-96d8fad51d40)
Message: daemon config changed (source=startup)
Time: 6 hours, 36 minutes ago
Metadata: source: startup, type: config_changed
[INFO] SYSTEM (922e1302-2d2f-4bda-9cf3-2d571107e880)
Message: Network map updated
Time: 6 hours, 36 minutes ago
[INFO] SYSTEM (9bae40c5-571c-4d40-9245-fe197c2f38bd)
Message: Network map updated
Time: 6 hours, 26 minutes ago
OS: linux/amd64
Daemon version: 0.79.0
CLI version: 0.79.0
Profile: default
Management: Connected to https://nb.anon-9Th8J.domain:443
Signal: Connected to https://nb.anon-9Th8J.domain:443
Relays:
[stun:nb.anon-9Th8J.domain:3478] is Available
[rels://nb.anon-9Th8J.domain:443] is Available via ws
Nameservers:
FQDN: nb.netbird.selfhosted
NetBird IP: 100.64.116.206/16
NetBird IPv6: 2001:db8:ffff::/64
Interface type: Kernel
Wireguard port: 49022
Quantum resistance: false
Lazy connection: true
SSH Server: Disabled
Networks: -
Peers count: 0/0 Connected
Create and upload a debug bundle, and share the returned file key:
netbird debug for 1m -AS -U
aa1fd1a05ed1f058cbd4b6fc939a97957cbac02ae15e0297b5011ff5e813f55a/587c1034-c319-4213-b4c3-74fd2cb2791f
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
[root@nb ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
aa51245b4607 netbirdio/reverse-proxy:latest "/go/bin/netbird-pro…" 3 minutes ago Up 3 minutes 8443/tcp, 0.0.0.0:51820->51820/udp, [::]:51820->51820/udp netbird-proxy
8919e3b4a2d7 crowdsecurity/crowdsec:v1.7.7 "/bin/bash /docker_s…" 3 minutes ago Up 3 minutes (healthy) netbird-crowdsec
cb18ac31e80a traefik:v3.6 "/entrypoint.sh --lo…" 3 minutes ago Up 3 minutes 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp netbird-traefik
614fd212c890 netbirdio/dashboard:latest "/usr/bin/supervisor…" 3 minutes ago Restarting (139) 5 seconds ago netbird-dashboard
647b54b5cfee netbirdio/netbird-server:latest "/go/bin/netbird-ser…" 3 minutes ago Up 3 minutes 0.0.0.0:3478->3478/udp, [::]:3478->3478/udp netbird-server
[root@nb ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
141a829dd9b2 bridge bridge local
acf4b65e7a74 host host local
88b57d0bbb55 none null local
19d0724fa1ad root_netbird bridge local
[root@nb ~]# docker network inspect root_netbird | grep -A 2 Containers
"Containers": {
"647b54b5cfee65db36d94ca722805b4cd36350dbf079494e8b8442f33e55766d": {
"Name": "netbird-server",
[root@nb ~]# docker network inspect bridge | grep -A 2 Containers
"Containers": {},
"Status": {
"IPAM": {
I’m guessing it has something to do with the Docker network specified for the Netbird containers. Maybe local IP’s have been reassigned differently to the containers??? I’m saying this because I have encountered that issue with other Docker stacks, on other servers. The way I fixed it was to use the service names instead of the IP addresses in the reverse-proxy settings. Then if the IP’s assigned to the containers ever changed, everything still worked. Anyway, I really need help troubleshooting. I don’t know where to begin.
Have you tried these troubleshooting steps?
- Reviewed client troubleshooting (if applicable)
- Checked for newer NetBird versions
- Searched for similar issues on GitHub (including closed ones)
- Restarted the NetBird client
- Disabled other VPN software
- Checked firewall settings