[GH-ISSUE #2812] Zero peers after restart management service #6261

Open
opened 2026-08-05 01:07:30 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @netandreus on GitHub (Oct 30, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2812

Describe the problem

I have fresh installation of Self hosted Netbird , builded from quick start guide (with Zitadel). Netbird client installed on the same machine and It looks like it's connected.

$ netbird status
OS: linux/amd64
Daemon version: 0.30.2
CLI version: 0.30.2
Management: Connected
Signal: Connected
Relays: 3/3 Available
Nameservers: 0/0 Available
FQDN: node-0.netbird.selfhosted
NetBird IP: 100.81.205.48/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 9/11 Connected

To Reproduce

Restart management service:

cd /home/adin/netbird/current
docker compose stop
docker compose up -d

Expected behavior

All peers connected and listed in managmant UI.

Are you using NetBird Cloud?

I use self-host NetBird's control plane.

NetBird version

0.30.2

Screenshots

Screenshot 2024-10-30 at 17 25 45 Screenshot 2024-10-30 at 17 26 36

What have I already tried

  • Click to Refresh button in peers list
  • Restart containers one more time
  • Restore VMWare snapshot with this VM
  • Upgrade NetBird Self-Hosted to the latest version
  • Logout and login
Originally created by @netandreus on GitHub (Oct 30, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2812 **Describe the problem** I have fresh installation of Self hosted Netbird , builded from quick start guide (with Zitadel). Netbird client installed on the same machine and It looks like it's connected. ``` $ netbird status OS: linux/amd64 Daemon version: 0.30.2 CLI version: 0.30.2 Management: Connected Signal: Connected Relays: 3/3 Available Nameservers: 0/0 Available FQDN: node-0.netbird.selfhosted NetBird IP: 100.81.205.48/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 9/11 Connected ``` **To Reproduce** Restart management service: ```bash cd /home/adin/netbird/current docker compose stop docker compose up -d ``` **Expected behavior** All peers connected and listed in managmant UI. **Are you using NetBird Cloud?** I use self-host NetBird's control plane. **NetBird version** 0.30.2 **Screenshots** <img width="1411" alt="Screenshot 2024-10-30 at 17 25 45" src="https://github.com/user-attachments/assets/87c93434-269a-48b7-a2c0-94693dfb441c"> <img width="1933" alt="Screenshot 2024-10-30 at 17 26 36" src="https://github.com/user-attachments/assets/a0db7605-3f4b-4a5a-bf90-6f219882e8d7"> **What have I already tried** - Click to Refresh button in peers list - Restart containers one more time - Restore VMWare snapshot with this VM - Upgrade NetBird Self-Hosted to the latest version - Logout and login
saavagebueno added the self-hosting label 2026-08-05 01:07:30 -04:00
Sign in to join this conversation.
No Label self-hosting
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#6261