Peers are not added to new user/client

[joao-aveiro]

Describe the problem

I have a self-hosted deployment of Netbird, with Google Cloud/Workspace as the IdP. The majority of existing users were added in version 0.29.x, but it is currently running version 0.30.3. A new user just signed up and I assigned groups similarly to other users; however, this new user can't connect to any other peer and in both the "Accessible Peers" table in the management GUI and by running netbird status -d only 2 peers appear, instead of the expected 10+. Also, these two peers that show up are other users and not the expected machines in our internal compute infrastructure.

To Reproduce

• Add new user in self-hosted Netbird + Google Cloud/Workspace IdP
• Add groups to the user, with existing policies allowign access to other peers

Expected behavior

The target peers should be accessible if the user is assigned the correct group and there are policies in place for this.

Are you using NetBird Cloud?

No, self-hosted NetBird.

NetBird version

Tested multiple combinations of versions 0.30.2 and 0.30.3 for the client and server.

[joao-aveiro]

I've tried to:

• Restart the server
• Restart the service and client on the user's side
• Disable and re-enable all the policies related with these groups
• Block and unblock the user in question
• Delete the user's peer and require re-authentication

Nothing helped.

[bcmmbaga]

Hello @joao-aveiro Do you have any applied posture checks on the policy? Also, could you confirm if user group propagation in Settings > Groups is enabled?

Additionally, can you confirm if the group assigned to the user was also added to the peer?

[mlsmaycon]

any feedback @joao-aveiro ?

[noerdar]

I have the same issue i think. I have a peer that advertises routes. If a new client joins the network, the peer that advertises routes does not get this new peer client, so when the client tries to contract that network, it does not work until the peer that advertises the routes are restartet with a netbird down and after netbird up, it finds all the client peers. So the Peers count: 2/5 Connected does not find the new client so i would be 3/6 in that scneario.

OS: linux/amd64 Daemon version: 0.31.0 CLI version: 0.31.0 Management: Connected to https://netbirdvpn.domain.com:443 Signal: Connected to https://netbirdvpn.domain.com:443 Relays: [stun:netbirdvpn.domain.com:3478] is Available [turn:netbirdvpn.domain.com:3478?transport=udp] is Available [rels://netbirdvpn.domain.com:443] is Available Nameservers: [172.16.20.4:53, 192.168.140.1:53] for [domain.com] is Available FQDN: netbird01.netbird.selfhosted NetBird IP: 100.86.156.178/16 Interface type: Kernel Quantum resistance: false Routes: 192.168.1.10/24, 192.168.1.12/24 Peers count: 2/5 Connected