[GH-ISSUE #4904] Unable to ssh to resource after policy change #10332

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

Originally created by @gwirn on GitHub (Dec 3, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4904

Describe the problem

I have a peer A, a routing peer R and a resource X. A can not reach X without netbird. Furthermore I created a policy that lets A access X via R (Protocol : ALL, no posture checks,source is a group where A is a member of, destination is a group where X is a memeber of). When this is enabled I can ssh user@myserver without any problems. When I now disable the policy and re-enable it, ssh user@myserver does not work (ssh: connect to host myserver port 22: No route to host). In order to be able to ssh from A into X again I have to restart the netbird client on A with netbird downfollowed bynetbird up`.

docker compose logs management shows only the grpc context ended early, error context canceled it shows upon netbird down

EDIT:
netbird networks list on A
shows the resource as Available Networks (before restart of the netbird client) even though ssh into the resource X does not work before restart

The most similar issue I found is #4769

To Reproduce

Steps to reproduce the behavior:

  1. Go to Policies and create a policy allowing the connection of a peer to a resource it usually can not access
  2. ssh user@resouce (SSH SUCCESSFUL)
  3. disable the policy
  4. enable the policy
  5. ssh user@resource (SSH UNSUCCESSFUL)
  6. no connection possible
  7. netbird down
  8. netbird up
  9. ssh user@resouce (SSH SUCCESSFUL)

Expected behavior

SSH connection works without the need to restart the netbird client

Are you using NetBird Cloud?

self-host

NetBird version

0.60.4

** OS **
Linux Mint 22.1

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 @gwirn on GitHub (Dec 3, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4904 **Describe the problem** I have a peer `A`, a routing peer `R` and a resource `X`. `A` can not reach `X` without netbird. Furthermore I created a policy that lets `A` access `X` via `R` (Protocol : ALL, no posture checks,source is a group where `A` is a member of, destination is a group where `X` is a memeber of). When this is enabled I can `ssh user@myserver` without any problems. When I now disable the policy and re-enable it, `ssh user@myserver` does not work (`ssh: connect to host myserver port 22: No route to host`). In order to be able to ssh from `A` into `X` again I have to restart the netbird client on `A with `netbird down` followed by `netbird up`. `docker compose logs management` shows only the `grpc context ended early, error context canceled` it shows upon `netbird down` EDIT: `netbird networks list` on `A` shows the resource as Available Networks (before restart of the netbird client) even though ssh into the resource `X` does not work before restart The most similar issue I found is #4769 **To Reproduce** Steps to reproduce the behavior: 1. Go to `Policies` and create a policy allowing the connection of a peer to a resource it usually can not access 2. ssh user@resouce (SSH SUCCESSFUL) 3. disable the policy 4. enable the policy 5. ssh user@resource (SSH UNSUCCESSFUL) 6. no connection possible 7. `netbird down` 8. `netbird up` 9. ssh user@resouce (SSH SUCCESSFUL) **Expected behavior** SSH connection works without the need to restart the netbird client **Are you using NetBird Cloud?** self-host **NetBird version** `0.60.4` ** OS ** `Linux Mint 22.1` **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:25:28 -04:00
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#10332