Management server goes down, takes the entire fleet of peers with it #1897

Open
opened 2025-11-20 06:08:45 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @rihards-simanovics on GitHub (May 19, 2025).

A couple of releases ago, I noticed that when the management server briefly goes down for maintenance (docker restart or upgrade), all peers immediately drop their connection to others, despite showing a P2P connection before that.

When I switched from a traditional VPN to Netbird, I specifically wanted to ensure that if the management peer goes down, this exact scenario doesn't happen. In fact, that was the case when I initially set up Netbird, and it has been that way until fairly recently.

A couple of years ago, the management server went down during the night, but the other peers continued to operate based on their last known configuration from the management server.

Now, when it goes down during the night, so do all of the other peers (mostly Linux and Windows).

The configs have stayed almost the same since the initial setup, with the exception of an occasional sync with the Zitadel installation script from GitHub releases.

I am happy to share the configs from my server if you can specify which ones would be applicable.

Originally created by @rihards-simanovics on GitHub (May 19, 2025). A couple of releases ago, I noticed that when the management server briefly goes down for maintenance (docker restart or upgrade), all peers immediately drop their connection to others, despite showing a P2P connection before that. When I switched from a traditional VPN to Netbird, I specifically wanted to ensure that if the management peer goes down, this exact scenario doesn't happen. In fact, that was the case when I initially set up Netbird, and it has been that way until fairly recently. A couple of years ago, the management server went down during the night, but the other peers continued to operate based on their last known configuration from the management server. Now, when it goes down during the night, so do all of the other peers (mostly Linux and Windows). The configs have stayed almost the same since the initial setup, with the exception of an occasional sync with the Zitadel installation script from GitHub releases. I am happy to share the configs from my server if you can specify which ones would be applicable.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1897