[GH-ISSUE #3316] no SSO provider returned from management #6792

Closed
opened 2026-08-05 01:10:08 -04:00 by saavagebueno · 7 comments
Owner

Originally created by @IanMoroney on GitHub (Feb 13, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3316

Describe the problem

Been using netbird for nearly a year and just started experiencing this issue. I'm not sure what kind of change led to this error, but oddly enough it's only affecting mac clients, and not the windows ones, so that seems to rule out the management server.

macOS Sequoia 15.3.1 (latest update as of today), and also happened before this latest update, so probably 15.3.0, all of our mac clients are facing this error when reconnecting to netbird after having been disconnected.

Only a reboot seems to workaround the issue, but our clients time out twice a day, so that's two reboots every day now, just to continue working.

netbird up

2025-02-13T09:07:04Z WARN client/cmd/root.go:247: retrying Login to the Management service in 753.932035ms due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys
2025-02-13T09:07:05Z WARN client/cmd/root.go:247: retrying Login to the Management service in 1.20722387s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys

Are you using NetBird Cloud?

self-hosted

NetBird version

0.36.5

NetBird status -dA output:

Daemon status: LoginFailed

Do you face any (non-mobile) client issues?

Please provide the file created by netbird debug for 1m -AS.

netbird debug for 1m -AS
Error: failed to up: up already in progress: current status LoginFailed

Additional context

We have a number of windows clients running the same version, and not experiencing the issue.

I also just tried updating to 0.36.6 which got released yesterday, and I'm still experiencing the issue.

Originally created by @IanMoroney on GitHub (Feb 13, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3316 **Describe the problem** Been using netbird for nearly a year and just started experiencing this issue. I'm not sure what kind of change led to this error, but oddly enough it's only affecting mac clients, and not the windows ones, so that seems to rule out the management server. macOS Sequoia 15.3.1 (latest update as of today), and also happened before this latest update, so probably 15.3.0, all of our mac clients are facing this error when reconnecting to netbird after having been disconnected. Only a reboot seems to workaround the issue, but our clients time out twice a day, so that's two reboots every day now, just to continue working. ``` netbird up 2025-02-13T09:07:04Z WARN client/cmd/root.go:247: retrying Login to the Management service in 753.932035ms due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys 2025-02-13T09:07:05Z WARN client/cmd/root.go:247: retrying Login to the Management service in 1.20722387s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys ``` **Are you using NetBird Cloud?** self-hosted **NetBird version** `0.36.5` **NetBird status -dA output:** `Daemon status: LoginFailed` **Do you face any (non-mobile) client issues?** Please provide the file created by `netbird debug for 1m -AS`. ``` netbird debug for 1m -AS Error: failed to up: up already in progress: current status LoginFailed ``` **Additional context** We have a number of windows clients running the same version, and not experiencing the issue. I also just tried updating to 0.36.6 which got released yesterday, and I'm still experiencing the issue.
saavagebueno added the triage-needed label 2026-08-05 01:10:08 -04:00
Author
Owner

@IanMoroney commented on GitHub (Feb 13, 2025):

I've also tried:
netbird service stop / netbird service start
netbird service uninstall / netbird service install
killing all netbird processes on mac

Nothing works around the problem other than a reboot.

<!-- gh-comment-id:2656001271 --> @IanMoroney commented on GitHub (Feb 13, 2025): I've also tried: netbird service stop / netbird service start netbird service uninstall / netbird service install killing all netbird processes on mac Nothing works around the problem other than a reboot.
Author
Owner

@ConaghFM commented on GitHub (Feb 13, 2025):

I'm experiencing the same issue:

$ netbird up
2025-02-13T08:42:42Z WARN client/cmd/root.go:247: retrying Login to the Management service in 1.243246494s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys
2025-02-13T08:42:43Z WARN client/cmd/root.go:247: retrying Login to the Management service in 878.326851ms due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys
2025-02-13T08:42:44Z WARN client/cmd/root.go:247: retrying Login to the Management service in 1.58234268s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys
2025-02-13T08:42:46Z WARN client/cmd/root.go:247: retrying Login to the Management service in 2.78866912s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys
2025-02-13T08:42:49Z WARN client/cmd/root.go:247: retrying Login to the Management service in 5.368929044s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys
2025-02-13T08:42:55Z WARN client/cmd/root.go:247: retrying Login to the Management service in 10.676670716s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys
Error: login backoff cycle failed: rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys

Initially happened with client version 0.33, did a complete uninstall and fresh install of 0.36.5, but no change.
I'm running MacOS Sequoia Version 15.2 (24C101).

Reboots work for me too, but something interesting I noticed is: one time I ran netbird up, and started the reboot without cancelling the netbird up command - it was still retrying with the backoff process. Most applications closed in preparation for the reboot, but one failed to close, and interrupted the shutdown process - it may have been the command still running in the terminal. Then, without my intervention, the login process succeeded on the next backoff iteration, and netbird came up. So it may be that some other application I had open was causing the issue, or something else which is changed in preparation for reboot, other than the reboot itself.
I'll try to replicate this next time it happens.

<!-- gh-comment-id:2656034984 --> @ConaghFM commented on GitHub (Feb 13, 2025): I'm experiencing the same issue: ``` $ netbird up 2025-02-13T08:42:42Z WARN client/cmd/root.go:247: retrying Login to the Management service in 1.243246494s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys 2025-02-13T08:42:43Z WARN client/cmd/root.go:247: retrying Login to the Management service in 878.326851ms due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys 2025-02-13T08:42:44Z WARN client/cmd/root.go:247: retrying Login to the Management service in 1.58234268s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys 2025-02-13T08:42:46Z WARN client/cmd/root.go:247: retrying Login to the Management service in 2.78866912s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys 2025-02-13T08:42:49Z WARN client/cmd/root.go:247: retrying Login to the Management service in 5.368929044s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys 2025-02-13T08:42:55Z WARN client/cmd/root.go:247: retrying Login to the Management service in 10.676670716s due to error rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys Error: login backoff cycle failed: rpc error: code = Unknown desc = no SSO provider returned from management. Please proceed with setting up this device using setup keys https://docs.netbird.io/how-to/register-machines-using-setup-keys ``` Initially happened with client version `0.33`, did a complete uninstall and fresh install of `0.36.5`, but no change. I'm running MacOS Sequoia Version 15.2 (24C101). Reboots work for me too, but something interesting I noticed is: one time I ran `netbird up`, and started the reboot without cancelling the `netbird up` command - it was still retrying with the backoff process. Most applications closed in preparation for the reboot, but one failed to close, and interrupted the shutdown process - it may have been the command still running in the terminal. Then, without my intervention, the login process succeeded on the next backoff iteration, and netbird came up. So it may be that some other application I had open was causing the issue, or something else which is changed in preparation for reboot, other than the reboot itself. I'll try to replicate this next time it happens.
Author
Owner

@mlsmaycon commented on GitHub (Feb 13, 2025):

@IanMoroney @ConaghFM, could you please share the agent logs for the devices affected?

You can get them with the guide from: https://docs.netbird.io/how-to/troubleshooting-client#getting-client-logs

Can you also confirm the NetBird management service version? You can get that with: docker inspect <management_container_id> | grep -i version

<!-- gh-comment-id:2656619791 --> @mlsmaycon commented on GitHub (Feb 13, 2025): @IanMoroney @ConaghFM, could you please share the agent logs for the devices affected? You can get them with the guide from: https://docs.netbird.io/how-to/troubleshooting-client#getting-client-logs Can you also confirm the NetBird management service version? You can get that with: `docker inspect <management_container_id> | grep -i version`
Author
Owner

@IanMoroney commented on GitHub (Feb 14, 2025):

So, it turns out it was vs code :)

For some reason, it's picked up port 53000 for auto-forward, which blocks netbird from receiving the sso response.

in vscode settings, you can exclude the port:

  "remote.portsAttributes": {
		"53000": {
			"label": "Netbird",
			"onAutoForward": "ignore",
		}
	},
<!-- gh-comment-id:2658764792 --> @IanMoroney commented on GitHub (Feb 14, 2025): So, it turns out it was vs code :) For some reason, it's picked up port 53000 for auto-forward, which blocks netbird from receiving the sso response. in vscode settings, you can exclude the port: ``` "remote.portsAttributes": { "53000": { "label": "Netbird", "onAutoForward": "ignore", } }, ```
Author
Owner

@IanMoroney commented on GitHub (Feb 14, 2025):

Image

<!-- gh-comment-id:2658767861 --> @IanMoroney commented on GitHub (Feb 14, 2025): ![Image](https://github.com/user-attachments/assets/ee819364-ac05-42fe-864d-10d66e3ffc75)
Author
Owner

@mlsmaycon commented on GitHub (Feb 14, 2025):

Thanks @IanMoroney for sharing the outcome.

The error log is misleading and we should fix that too.

<!-- gh-comment-id:2659764866 --> @mlsmaycon commented on GitHub (Feb 14, 2025): Thanks @IanMoroney for sharing the outcome. The error log is misleading and we should fix that too.
Author
Owner

@hgnme commented on GitHub (Oct 2, 2025):

So, it turns out it was vs code :)

For some reason, it's picked up port 53000 for auto-forward, which blocks netbird from receiving the sso response.

in vscode settings, you can exclude the port:

  "remote.portsAttributes": {
		"53000": {
			"label": "Netbird",
			"onAutoForward": "ignore",
		}
	},

Oh my god.... I spent most of a day on this. Thank you @IanMoroney. I had VSCode open the whole time (even after rebooting) and couldn't figure out why two identical machines would/wouldn't work.

VSCode was eating port 53000 just as you mentioned

<!-- gh-comment-id:3359163982 --> @hgnme commented on GitHub (Oct 2, 2025): > So, it turns out it was vs code :) > > For some reason, it's picked up port 53000 for auto-forward, which blocks netbird from receiving the sso response. > > in vscode settings, you can exclude the port: > > ``` > "remote.portsAttributes": { > "53000": { > "label": "Netbird", > "onAutoForward": "ignore", > } > }, > ``` Oh my god.... I spent most of a day on this. Thank you @IanMoroney. I had VSCode open the whole time (even after rebooting) and couldn't figure out why two identical machines would/wouldn't work. VSCode was eating port 53000 just as you mentioned
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#6792