Windows client not connect

[sgm456]

The Windows client doesn't connect to the Netbird server on versions 0.58 and 0.58.1.
The latest working version is 0.57.1.

A clear and concise description of what the problem is.

To Reproduce

Steps to reproduce the behavior:

1. Install agent on windows
2. See error

[sunstarjeff]

I came to the Issues page today to see if anyone had reported this issue, after experiencing connectivity issues on several Windows clients.

I'm reverting Windows clients back to 0.57.1 until this issue can be resolved.

[mlsmaycon]

@sgm456 @sunstarjeff could you please share the upload key for the following command in recent versions:

netbird debug bundle --upload-bundle --anonymize

[sunstarjeff]

Sure, is this what you're needing?

C:\WINDOWS\SystemTemp\netbird.debug.1785713459.zip
Upload file key:
f79e391890ab27fb37c88b3b4be7011e22aa2e5ca6f38ffa9c4481884941f726/fe13d424-65ed-4442-81f7-cbfa604d1254

[sgm456]

C:\tmp>netbird debug bundle --upload-bundle --anonymize Local file: C:\WINDOWS\SystemTemp\netbird.debug.1101652429.zip Upload file key: f79e391890ab27fb37c88b3b4be7011e22aa2e5ca6f38ffa9c4481884941f726/42c5f731-21bb-431c-a2fa-21c56434ee88

[lixmal]

Can you please run netbird debug for 1m -UA instead? Then share the upload file key again.
@sgm456 @sunstarjeff

Can you also describe what the issue is exactly? "See error" is not helpful

[mrwsl]

Our windows clients experience the same on version 0.58.0, while linux clients are not affected. Downgrading the windows clients to 0.57.1 helps. Here is the debug upload bundle:

Upload file key:
a43af7f29c88cc80d10dfbf4f3396dd4829a71a3edc2a76a38c81b747a819736/26b072dc-a7cd-4b1c-8fce-6e3a5b5b5a1e

EDIT: The "error" is that no device is connected to the client. They are showing 0/x connected.

[lixmal]

Thanks @mrwsl

For the time being you can downgrade like you did or set this env var:

netbird service reconfigure --service-env NB_USE_LEGACY_ROUTING=true

[sgm456]

C:\tmp>netbird service reconfigure --service-env NB_USE_LEGACY_ROUTING=true
Stopping NetBird service...
Removing existing service configuration...
Installing service with new configuration...
Starting NetBird service...
NetBird service has been reconfigured and started

C:\tmp>netbird debug for 1m -UA
Error: failed to set log level to TRACE: engine not initialized

C:\tmp>netbird debug for 1m -UA
netbird down
Error: failed to up: up already in progress: current status LoginFailed

After reverting to 0.57.1, I connected successfully.

[mlsmaycon]

@sgm456 can you confirm that the issue happens after a few seconds of running the reconfigure command? I mean, if you wait, 10-30 seconds before running netbird debug for 1m -U -A does it work?

[sgm456]

@sgm456 can you confirm that the issue happens after a few seconds of running the reconfigure command? I mean, if you wait, 10-30 seconds before running netbird debug for 1m -U -A does it work?

After 1 min connected. 0.58.1

[mlsmaycon]

@sgm456 thanks for the update. Can you generate the bundle with?

netbird debug for 2m -U -A

[davidchi2020]

I also encountered a very similar issue and noticed a possible pattern: After upgrading the NetBird client on one of my Windows PCs (PC1) from version 0.57.1 to 0.58.0 or 0.58.1, it lost connectivity with some other NetBird peers. These unreachable peers were running either Windows or Linux, and the connectivity issue didn’t seem related to their NetBird client versions. However, I found that if the unreachable peers actively pinged PC1’s NetBird domain name, the connection between them would be restored. Not sure if this observation could provide useful clues for troubleshooting.

[davidchi2020]

I also encountered a very similar issue and noticed a possible pattern: After upgrading the NetBird client on one of my Windows PCs (PC1) from version 0.57.1 to 0.58.0 or 0.58.1, it lost connectivity with some other NetBird peers. These unreachable peers were running either Windows or Linux, and the connectivity issue didn’t seem related to their NetBird client versions. However, I found that if the unreachable peers actively pinged PC1’s NetBird domain name, the connection between them would be restored. Not sure if this observation could provide useful clues for troubleshooting.

On two Windows 10 PCs, after upgrading NetBird from version 0.57.1 to 0.58.1, they were unable to establish a connection. Pinging each other did not help either. It seems the pattern I mentioned earlier was inaccurate—this is quite puzzling.

[sgm456]

C:\tmp>netbird debug for 2m -U -A netbird down netbird up Remaining time: 00:00:01 Duration completed Creating debug bundle... Local file: C:\WINDOWS\SystemTemp\netbird.debug.1260464448.zip Upload file key: f79e391890ab27fb37c88b3b4be7011e22aa2e5ca6f38ffa9c4481884941f726/445cb134-ba46-4b9e-82a1-3586402b0df1