[GH-ISSUE #5718] Activating or deactivating a Resource in a Network does not propagate to peers until peers restart netbird #11913

Closed
opened 2026-08-05 01:31:35 -04:00 by saavagebueno · 1 comment
Owner

Originally created by @tsenovIvan on GitHub (Mar 27, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5718

Describe the problem

Activating or deactivating a Resource in a Network does not propagate to peers until peers restart netbird service.
Used to work perfectly, but it is now broken.

To Reproduce

Steps to reproduce the behavior:

  1. Start with a Disabled resource
  2. Activate it
  3. Peers cannot access it - no routing
  4. Restart a peer - this peer now has routing to Resource

There is also similar problem with the routing peer.
You can Disable a resource, but the routing peer is still being able to route to it, until you restart the routing peer.

As a whole - activating / deactivating a Resource does not propagate to routing peer and peers which are allowed to access the Resource.

Expected behavior

Activating / Deactivating a resource should in a reasonable time propagate to affected peers.

Are you using NetBird Cloud?

No

NetBird version

0.67.1 on all peers and server

Is any other VPN software installed?

N

Debug output

To help us resolve the problem, please attach the following anonymized status output

netbird status -dA

Create and upload a debug bundle, and share the returned file key:

netbird debug for 1m -AS -U

Uploaded files are automatically deleted after 30 days.

Alternatively, create the file only and attach it here manually:

netbird debug for 1m -AS

Screenshots

If applicable, add screenshots to help explain your problem.

This used to work several versions ago, but I cannot give certain version. I'm sure it worked, because I use it regularly, because I need access to these resource, but for a security reason I do not allow all resources constantly, but enable them only when I need them.

Add any other context about the problem here.

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
Originally created by @tsenovIvan on GitHub (Mar 27, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5718 **Describe the problem** Activating or deactivating a Resource in a Network does not propagate to peers until peers restart netbird service. Used to work perfectly, but it is now broken. **To Reproduce** Steps to reproduce the behavior: 1. Start with a Disabled resource 2. Activate it 3. Peers cannot access it - no routing 4. Restart a peer - this peer now has routing to Resource There is also similar problem with the routing peer. You can Disable a resource, but the routing peer is still being able to route to it, until you restart the routing peer. As a whole - activating / deactivating a Resource does not propagate to routing peer and peers which are allowed to access the Resource. **Expected behavior** Activating / Deactivating a resource should in a reasonable time propagate to affected peers. **Are you using NetBird Cloud?** No **NetBird version** 0.67.1 on all peers and server **Is any other VPN software installed?** N **Debug output** To help us resolve the problem, please attach the following anonymized status output netbird status -dA Create and upload a debug bundle, and share the returned file key: netbird debug for 1m -AS -U *Uploaded files are automatically deleted after 30 days.* Alternatively, create the file only and attach it here manually: netbird debug for 1m -AS **Screenshots** If applicable, add screenshots to help explain your problem. This used to work several versions ago, but I cannot give certain version. I'm sure it worked, because I use it regularly, because I need access to these resource, but for a security reason I do not allow all resources constantly, but enable them only when I need them. Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [X] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [X] Checked for newer NetBird versions - [X] Searched for similar issues on GitHub (including closed ones) - [X] Restarted the NetBird client - [ ] Disabled other VPN software - [X] Checked firewall settings
saavagebueno added the triage-needed label 2026-08-05 01:31:35 -04:00
Author
Owner

@tsenovIvan commented on GitHub (Apr 30, 2026):

With some of the v0.70.x updates this seems to be working again.

<!-- gh-comment-id:4353020684 --> @tsenovIvan commented on GitHub (Apr 30, 2026): With some of the v0.70.x updates this seems to be working again.
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11913