Clients that have connected, will be required to re-authenticate, the following pattern is what we are seeing:
Peer 1
Day 1 - Connects
Day 2 - Gets Successful Login, but Netbird states it fails, after 3 tries they get connected
Day 3 - Connects
Day 4 - Connects
Day 5 - Gets Successful Login, but Netbird states it fails, after 3 tries they get connected
Peer 2
Day 1 - Connects
Day 2 - Connects
Day 3 - Connects
Day 4 - Connects
Day 5 - Gets Successful Login, but Netbird states it fails, will not longer connect had to setup as Setup Key
Peer 3
Day 1 - Gets Successful Login, but Netbird states it fails, after 3 tries they get connected
Day 2 - Connects
Day 3 - Gets Successful Login, but Netbird states it fails, after 2 tries they get connected
Day 4 - Connects
Day 5 - Gets Successful Login, but Netbird states it fails, after 3 tries they get connected
We have 6 connections that are not having issues connecting at all
Each time the connection fails we get the following on the client: Error: daemon up failed: sso login failed: waiting sso login failed with: rpc error: code = InvalidArgument desc = invalid jwt token, err: token could not be parsed: Token is expired
Most machines are running Windows 10, no other VPN software installed and updates are all up to date. And clients are running the same version as the server.
Are you using NetBird Cloud?
No - Self Hosted - Ubuntu / AWS Server
NetBird version
54.2
Is any other VPN software installed?
No