SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-28 02:52:06 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Netbird service 0.36.x and newer freezes on Windows #1643

New Issue
Closed
opened 2025-11-20 06:03:59 -05:00 by saavagebueno · 21 comments
saavagebueno commented 2025-11-20 06:03:59 -05:00
Owner
Copy Link

Originally created by @tomashora on GitHub (Feb 21, 2025).

Originally assigned to: @pappz on GitHub.

Describe the problem

After updating to 0.37.0 (and 0.37.1 as well) this message appeared only once right after connection, but once the connection to the DNS server within netbird universe is estabilished, the message disappeared.

However after putting laptop to sleep and turning on again, this message appears around every 5seconds and the netbird service is fozen thus cannot generate the debug logs.

The service had to be force-killed using taskkill /pid PID /f (restart using netbird service restart did not finished) so the attached debug log is from the time after service restart.

SelfHosted

NetBird version

0.37 client

NetBird status -dA output:

could not be generated

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

could not be generated

Screenshots

Image

Image

Additional context

Add any other context about the problem here.

Current stat.json content: {"dns_state":null,"route_state":{"refCountMap":{},"idMap":{}},"routeselector_state":null}

netbird.debug.4066958341.zip

Originally created by @tomashora on GitHub (Feb 21, 2025). Originally assigned to: @pappz on GitHub. **Describe the problem** After updating to 0.37.0 (and 0.37.1 as well) this message appeared only once right after connection, but once the connection to the DNS server within netbird universe is estabilished, the message disappeared. However after putting laptop to sleep and turning on again, this message appears around every 5seconds and the netbird service is fozen thus cannot generate the debug logs. The service had to be force-killed using ```taskkill /pid PID /f``` (restart using netbird service restart did not finished) so the attached debug log is from the time after service restart. SelfHosted **NetBird version** 0.37 client **NetBird status -dA output:** could not be generated **Do you face any (non-mobile) client issues?** could not be generated **Screenshots** ![Image](https://github.com/user-attachments/assets/8c36da30-99fc-4f95-a299-65e039f0244b) ![Image](https://github.com/user-attachments/assets/9bb6faaf-65cb-487d-898f-1ced5f3e2c1b) **Additional context** Add any other context about the problem here. Current stat.json content: ```{"dns_state":null,"route_state":{"refCountMap":{},"idMap":{}},"routeselector_state":null}``` [netbird.debug.4066958341.zip](https://github.com/user-attachments/files/18916189/netbird.debug.4066958341.zip)
saavagebueno added the triage-needed label 2025-11-20 06:03:59 -05:00
saavagebueno commented 2025-11-20 06:04:00 -05:00
Author
Owner
Copy Link

@Oriann commented on GitHub (Feb 23, 2025):

Facing same problem

netbird.debug.2399991544.zip

@Oriann commented on GitHub (Feb 23, 2025): Facing same problem [netbird.debug.2399991544.zip](https://github.com/user-attachments/files/18929615/netbird.debug.2399991544.zip)
saavagebueno commented 2025-11-20 06:04:00 -05:00
Author
Owner
Copy Link

@boopzz commented on GitHub (Feb 24, 2025):

I believe we have the same problem. Previously we had matched domains working, upgraded from v0.36.7 to v0.37.1. At first everything seemed to be working and now the DNS services have an `i/o timeout" error and we are unable to resolve. However we cant route any traffic beyond the peer. We can connect to the peer fine and the peer has all the correct connectivity but the peers wont route traffic for some reason.

Are you able to route any traffic at all?

EDIT: Mine was a separate issue to do with the firewall implementation

@boopzz commented on GitHub (Feb 24, 2025): I believe we have the same problem. Previously we had matched domains working, upgraded from v0.36.7 to v0.37.1. At first everything seemed to be working and now the DNS services have an `i/o timeout" error and we are unable to resolve. However we cant route any traffic beyond the peer. We can connect to the peer fine and the peer has all the correct connectivity but the peers wont route traffic for some reason. Are you able to route any traffic at all? EDIT: Mine was a separate issue to do with the firewall implementation
saavagebueno commented 2025-11-20 06:04:00 -05:00
Author
Owner
Copy Link

@tomashora commented on GitHub (Feb 28, 2025):

Reported by multiple users - happens regullary. Attached debug bundle after force-killing the service.
netbird.debug.2157308570.zip

@tomashora commented on GitHub (Feb 28, 2025): Reported by multiple users - happens regullary. Attached debug bundle after force-killing the service. [netbird.debug.2157308570.zip](https://github.com/user-attachments/files/19026938/netbird.debug.2157308570.zip)
saavagebueno commented 2025-11-20 06:04:01 -05:00
Author
Owner
Copy Link

@iamjustcurious commented on GitHub (Feb 28, 2025):

Unfortunately, we are also facing the problem

@iamjustcurious commented on GitHub (Feb 28, 2025): Unfortunately, we are also facing the problem
saavagebueno commented 2025-11-20 06:04:01 -05:00
Author
Owner
Copy Link

@cleveHEX commented on GitHub (Mar 5, 2025):

Colleagues that did not update their client do not have this issue. Person on 0.34.x does not face this issue, I face it on 0.36.x and 0.37.x.

@cleveHEX commented on GitHub (Mar 5, 2025): Colleagues that did not update their client do not have this issue. Person on 0.34.x does not face this issue, I face it on 0.36.x and 0.37.x.
saavagebueno commented 2025-11-20 06:04:01 -05:00
Author
Owner
Copy Link

@tomashora commented on GitHub (Mar 9, 2025):

Still happening also on 0.37.2

netbird.debug.3307782300.zip

@tomashora commented on GitHub (Mar 9, 2025): Still happening also on 0.37.2 [netbird.debug.3307782300.zip](https://github.com/user-attachments/files/19152209/netbird.debug.3307782300.zip)
saavagebueno commented 2025-11-20 06:04:01 -05:00
Author
Owner
Copy Link

@tomashora commented on GitHub (Mar 10, 2025):

Could this be related? Noticed this after enabling notifications...

Image

netbird.debug.2640559806.zip

The client.log says:

2025-03-10T08:44:39+01:00 PANC client/internal/connect.go:118: Panic occurred: close of closed channel, stack trace: goroutine 1228322 [running]:
runtime/debug.Stack()
	/opt/hostedtoolcache/go/1.23.6/x64/src/runtime/debug/stack.go:26 +0x5e
github.com/netbirdio/netbird/client/internal.(*ConnectClient).run.func1()
	/home/runner/work/netbird/netbird/client/internal/connect.go:118 +0x7c
panic({0x158ad40?, 0x1943fd0?})
	/opt/hostedtoolcache/go/1.23.6/x64/src/runtime/panic.go:785 +0x132
github.com/netbirdio/netbird/client/firewall/uspfilter/conntrack.(*UDPTracker).Close(0xc001e5dd60)
	/home/runner/work/netbird/netbird/client/firewall/uspfilter/conntrack/udp.go:135 +0x48
github.com/netbirdio/netbird/client/firewall/uspfilter.(*Manager).Close(0xc001010d00, 0x0?)
	/home/runner/work/netbird/netbird/client/firewall/uspfilter/allow_netbird_windows.go:32 +0xed
github.com/netbirdio/netbird/client/internal.(*Engine).close(0xc0007a2488)
	/home/runner/work/netbird/netbird/client/internal/engine.go:1365 +0x223
github.com/netbirdio/netbird/client/internal.(*Engine).Stop(0xc0007a2488)
	/home/runner/work/netbird/netbird/client/internal/engine.go:301 +0x2ea
github.com/netbirdio/netbird/client/internal.(*ConnectClient).run.func3()
	/home/runner/work/netbird/netbird/client/internal/connect.go:295 +0x14ed
github.com/cenkalti/backoff/v4.RetryNotifyWithTimer.Operation.withEmptyData.func1()
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:18 +0x13
github.com/cenkalti/backoff/v4.doRetryNotify[...](0xc003e3f9a8?, {0x194e398, 0xc001ca2720}, 0x0, {0x0, 0x0?})
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:88 +0x11c
github.com/cenkalti/backoff/v4.RetryNotifyWithTimer(0xc003ab8280?, {0x194e398?, 0xc001ca2720?}, 0x7c1a4b4aea9c106b?, {0x0?, 0x0?})
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:61 +0x56
github.com/cenkalti/backoff/v4.RetryNotify(...)
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:49
github.com/cenkalti/backoff/v4.Retry(...)
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:38
github.com/netbirdio/netbird/client/internal.(*ConnectClient).run(0xc0021b0380, {{0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0, 0x0}, ...}, ...)
	/home/runner/work/netbird/netbird/client/internal/connect.go:315 +0x475
github.com/netbirdio/netbird/client/internal.(*ConnectClient).Run(...)
	/home/runner/work/netbird/netbird/client/internal/connect.go:65
github.com/netbirdio/netbird/client/server.(*Server).connectWithRetryRuns.func2()
	/home/runner/work/netbird/netbird/client/server/server.go:196 +0x185
github.com/cenkalti/backoff/v4.RetryNotifyWithTimer.Operation.withEmptyData.func1()
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:18 +0x13
github.com/cenkalti/backoff/v4.doRetryNotify[...](0xc003e3feb0?, {0x299768d51f8, 0xc004480240}, 0x0, {0x0, 0x0?})
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:88 +0x11c
github.com/cenkalti/backoff/v4.RetryNotifyWithTimer(0x1957ae8?, {0x299768d51f8?, 0xc004480240?}, 0x1021145?, {0x0?, 0x0?})
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:61 +0x56
github.com/cenkalti/backoff/v4.RetryNotify(...)
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:49
github.com/cenkalti/backoff/v4.Retry(...)
	/home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:38
github.com/netbirdio/netbird/client/server.(*Server).connectWithRetryRuns(0xc0004a4488, {0x1957ae8, 0xc00058b440}, 0xc00517c360, 0xc00048c780, 0xc0045a82a0)
	/home/runner/work/netbird/netbird/client/server/server.go:214 +0x194
created by github.com/netbirdio/netbird/client/server.(*Server).Up in goroutine 1228321
	/home/runner/work/netbird/netbird/client/server/server.go:632 +0x6d6
@tomashora commented on GitHub (Mar 10, 2025): Could this be related? Noticed this after enabling notifications... ![Image](https://github.com/user-attachments/assets/70b0f456-32c7-4362-b6e8-27d7ba1f4fd9) [netbird.debug.2640559806.zip](https://github.com/user-attachments/files/19158011/netbird.debug.2640559806.zip) The client.log says: ``` 2025-03-10T08:44:39+01:00 PANC client/internal/connect.go:118: Panic occurred: close of closed channel, stack trace: goroutine 1228322 [running]: runtime/debug.Stack() /opt/hostedtoolcache/go/1.23.6/x64/src/runtime/debug/stack.go:26 +0x5e github.com/netbirdio/netbird/client/internal.(*ConnectClient).run.func1() /home/runner/work/netbird/netbird/client/internal/connect.go:118 +0x7c panic({0x158ad40?, 0x1943fd0?}) /opt/hostedtoolcache/go/1.23.6/x64/src/runtime/panic.go:785 +0x132 github.com/netbirdio/netbird/client/firewall/uspfilter/conntrack.(*UDPTracker).Close(0xc001e5dd60) /home/runner/work/netbird/netbird/client/firewall/uspfilter/conntrack/udp.go:135 +0x48 github.com/netbirdio/netbird/client/firewall/uspfilter.(*Manager).Close(0xc001010d00, 0x0?) /home/runner/work/netbird/netbird/client/firewall/uspfilter/allow_netbird_windows.go:32 +0xed github.com/netbirdio/netbird/client/internal.(*Engine).close(0xc0007a2488) /home/runner/work/netbird/netbird/client/internal/engine.go:1365 +0x223 github.com/netbirdio/netbird/client/internal.(*Engine).Stop(0xc0007a2488) /home/runner/work/netbird/netbird/client/internal/engine.go:301 +0x2ea github.com/netbirdio/netbird/client/internal.(*ConnectClient).run.func3() /home/runner/work/netbird/netbird/client/internal/connect.go:295 +0x14ed github.com/cenkalti/backoff/v4.RetryNotifyWithTimer.Operation.withEmptyData.func1() /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:18 +0x13 github.com/cenkalti/backoff/v4.doRetryNotify[...](0xc003e3f9a8?, {0x194e398, 0xc001ca2720}, 0x0, {0x0, 0x0?}) /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:88 +0x11c github.com/cenkalti/backoff/v4.RetryNotifyWithTimer(0xc003ab8280?, {0x194e398?, 0xc001ca2720?}, 0x7c1a4b4aea9c106b?, {0x0?, 0x0?}) /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:61 +0x56 github.com/cenkalti/backoff/v4.RetryNotify(...) /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:49 github.com/cenkalti/backoff/v4.Retry(...) /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:38 github.com/netbirdio/netbird/client/internal.(*ConnectClient).run(0xc0021b0380, {{0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0, 0x0}, ...}, ...) /home/runner/work/netbird/netbird/client/internal/connect.go:315 +0x475 github.com/netbirdio/netbird/client/internal.(*ConnectClient).Run(...) /home/runner/work/netbird/netbird/client/internal/connect.go:65 github.com/netbirdio/netbird/client/server.(*Server).connectWithRetryRuns.func2() /home/runner/work/netbird/netbird/client/server/server.go:196 +0x185 github.com/cenkalti/backoff/v4.RetryNotifyWithTimer.Operation.withEmptyData.func1() /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:18 +0x13 github.com/cenkalti/backoff/v4.doRetryNotify[...](0xc003e3feb0?, {0x299768d51f8, 0xc004480240}, 0x0, {0x0, 0x0?}) /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:88 +0x11c github.com/cenkalti/backoff/v4.RetryNotifyWithTimer(0x1957ae8?, {0x299768d51f8?, 0xc004480240?}, 0x1021145?, {0x0?, 0x0?}) /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:61 +0x56 github.com/cenkalti/backoff/v4.RetryNotify(...) /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:49 github.com/cenkalti/backoff/v4.Retry(...) /home/runner/go/pkg/mod/github.com/cenkalti/backoff/v4@v4.3.0/retry.go:38 github.com/netbirdio/netbird/client/server.(*Server).connectWithRetryRuns(0xc0004a4488, {0x1957ae8, 0xc00058b440}, 0xc00517c360, 0xc00048c780, 0xc0045a82a0) /home/runner/work/netbird/netbird/client/server/server.go:214 +0x194 created by github.com/netbirdio/netbird/client/server.(*Server).Up in goroutine 1228321 /home/runner/work/netbird/netbird/client/server/server.go:632 +0x6d6 ```
saavagebueno commented 2025-11-20 06:04:01 -05:00
Author
Owner
Copy Link

@cleveHEX commented on GitHub (Mar 11, 2025):

@pappz I encounter similar behavior on 0.38.0

netbird.debug.4282123131.zip

@cleveHEX commented on GitHub (Mar 11, 2025): @pappz I encounter similar behavior on 0.38.0 [netbird.debug.4282123131.zip](https://github.com/user-attachments/files/19181842/netbird.debug.4282123131.zip)
saavagebueno commented 2025-11-20 06:04:01 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 12, 2025):

@pappz I encounter similar behavior on 0.38.0

netbird.debug.4282123131.zip

@cleveHEX, can you confirm if you just upgraded the client or if it was a fresh install? Also, what action did you take to restart the client?

Lastly, by any chance, when starting the client, do you click on Networks before Connect?

@mlsmaycon commented on GitHub (Mar 12, 2025): > [@pappz](https://github.com/pappz) I encounter similar behavior on 0.38.0 > > [netbird.debug.4282123131.zip](https://github.com/user-attachments/files/19181842/netbird.debug.4282123131.zip) @cleveHEX, can you confirm if you just upgraded the client or if it was a fresh install? Also, what action did you take to restart the client? Lastly, by any chance, when starting the client, do you click on Networks before Connect?
saavagebueno commented 2025-11-20 06:04:01 -05:00
Author
Owner
Copy Link

@Oriann commented on GitHub (Mar 12, 2025):

Facing same problem on 0.38.0, everytime I only update the client, restart is made via installer.

netbird.debug.3569783032.zip

@Oriann commented on GitHub (Mar 12, 2025): Facing same problem on 0.38.0, everytime I only update the client, restart is made via installer. [netbird.debug.3569783032.zip](https://github.com/user-attachments/files/19207229/netbird.debug.3569783032.zip)
saavagebueno commented 2025-11-20 06:04:02 -05:00
Author
Owner
Copy Link

@cleveHEX commented on GitHub (Mar 12, 2025):

@mlsmaycon I have upgraded the client, not a fresh install (the Netbird was not stuck before the upgrade). I kill netbird.exe, it restarts automatically and then it starts working, unloading via Windows Services does not work, the service gets stuck in stopping state infinitely.

I don't think so, I don't use this feature at all.

@cleveHEX commented on GitHub (Mar 12, 2025): @mlsmaycon I have upgraded the client, not a fresh install (the Netbird was not stuck before the upgrade). I kill `netbird.exe`, it restarts automatically and then it starts working, unloading via Windows Services does not work, the service gets stuck in stopping state infinitely. I don't think so, I don't use this feature at all.
saavagebueno commented 2025-11-20 06:04:02 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 12, 2025):

@Oriann @cleveHEX are you guys able to reproduce the issue by downgrading it to 0.37.2 and upgrading again? You can find the installers here:

037.2 -> https://github.com/netbirdio/netbird/releases/download/v0.37.2/netbird_installer_0.37.2_windows_amd64.exe
0.38.0 -> https://github.com/netbirdio/netbird/releases/download/v0.38.0/netbird_installer_0.38.0_windows_amd64.exe

@mlsmaycon commented on GitHub (Mar 12, 2025): @Oriann @cleveHEX are you guys able to reproduce the issue by downgrading it to 0.37.2 and upgrading again? You can find the installers here: 037.2 -> https://github.com/netbirdio/netbird/releases/download/v0.37.2/netbird_installer_0.37.2_windows_amd64.exe 0.38.0 -> https://github.com/netbirdio/netbird/releases/download/v0.38.0/netbird_installer_0.38.0_windows_amd64.exe
saavagebueno commented 2025-11-20 06:04:02 -05:00
Author
Owner
Copy Link

@Oriann commented on GitHub (Mar 12, 2025):

@mlsmaycon Yes still the same issue even after this test.

Steps I made:
1.Netbird running > ran installer, downgraded to 0.37.2
2. Netbird shows warning as OP described
3. Made debug bundle for 0.37.2
4.Netbird running > ran installer upgraded back to 0.38.0
5.Netbird shows the same warning as on previous version.
6. Made debug bundle for 0.38.0

netbird.debug.1729080692_0.38.0.zip
netbird.debug.4062680248_0.37.2.zip

@Oriann commented on GitHub (Mar 12, 2025): @mlsmaycon Yes still the same issue even after this test. Steps I made: 1.Netbird running > ran installer, downgraded to 0.37.2 2. Netbird shows warning as OP described 3. Made debug bundle for 0.37.2 4.Netbird running > ran installer upgraded back to 0.38.0 5.Netbird shows the same warning as on previous version. 6. Made debug bundle for 0.38.0 [netbird.debug.1729080692_0.38.0.zip](https://github.com/user-attachments/files/19207798/netbird.debug.1729080692_0.38.0.zip) [netbird.debug.4062680248_0.37.2.zip](https://github.com/user-attachments/files/19207800/netbird.debug.4062680248_0.37.2.zip)
saavagebueno commented 2025-11-20 06:04:02 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 12, 2025):

@Oriann, it's great that you can reproduce it; it will help us understand the issue better.

Can you enable trace logs before repeating the downgrade/upgrade steps? You can do that with:

[Environment]::SetEnvironmentVariable("NB_LOG_LEVEL", "debug", "Machine")

Then please share the logs again.

Also, the warning you are referencing to is the Panicking or the DNS?

@mlsmaycon commented on GitHub (Mar 12, 2025): @Oriann, it's great that you can reproduce it; it will help us understand the issue better. Can you enable trace logs before repeating the downgrade/upgrade steps? You can do that with: ```shell [Environment]::SetEnvironmentVariable("NB_LOG_LEVEL", "debug", "Machine") ``` Then please share the logs again. Also, the warning you are referencing to is the Panicking or the DNS?
saavagebueno commented 2025-11-20 06:04:02 -05:00
Author
Owner
Copy Link

@Oriann commented on GitHub (Mar 12, 2025):

@mlsmaycon ok i have enabled trace logs and attaching debug bundles

I am referencing to DNS issue, I have not succesfully reproduced panicking even when trying hibernate or sleep mode. But I am on PC so things difer from laptop.

netbird.debug.113234266_0.37.2.zip
netbird.debug.126377177_0.38.0.zip

@Oriann commented on GitHub (Mar 12, 2025): @mlsmaycon ok i have enabled trace logs and attaching debug bundles I am referencing to DNS issue, I have not succesfully reproduced panicking even when trying hibernate or sleep mode. But I am on PC so things difer from laptop. [netbird.debug.113234266_0.37.2.zip](https://github.com/user-attachments/files/19210173/netbird.debug.113234266_0.37.2.zip) [netbird.debug.126377177_0.38.0.zip](https://github.com/user-attachments/files/19210172/netbird.debug.126377177_0.38.0.zip)
saavagebueno commented 2025-11-20 06:04:02 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 12, 2025):

Thanks @Oriann . Just to confirm, during the upgrade your client received the alert and also freezes the GUI client?

@mlsmaycon commented on GitHub (Mar 12, 2025): Thanks @Oriann . Just to confirm, during the upgrade your client received the alert and also freezes the GUI client?
saavagebueno commented 2025-11-20 06:04:03 -05:00
Author
Owner
Copy Link

@Oriann commented on GitHub (Mar 12, 2025):

@mlsmaycon I only recieve the alert, GUI wont freeze, I have tested it right now again just in case

@Oriann commented on GitHub (Mar 12, 2025): @mlsmaycon I only recieve the alert, GUI wont freeze, I have tested it right now again just in case
saavagebueno commented 2025-11-20 06:04:03 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Mar 12, 2025):

Got it, thanks @Oriann, that is the expected behavior for private DNS since when you start the agent, you won't have connectivity to that particular private server until you connect to the routing peer that routes traffic to it.

You can also confirm that with the netbird status -d command. See output from your peer:

Nameservers: 
  [192.168.20.1:53] for [anon-cxxx2.domain, anon-gUfys.domain] is Available
  [10.0.0.1:53] for [.] is Available
  [172.16.3.200:53, 172.16.3.202:53] for [ad.anon-zffBq.domain] is Available

To disable the debug logs you can run:

[Environment]::SetEnvironmentVariable("NB_LOG_LEVEL", "info", "Machine")

@cleveHEX As we couldn't reproduce the issue, it would be great if you could run the tests we described before with the debug logs.

In the meantime, I will close this issue and we can either open a new one or reopen this one to proceed.

@mlsmaycon commented on GitHub (Mar 12, 2025): Got it, thanks @Oriann, that is the expected behavior for private DNS since when you start the agent, you won't have connectivity to that particular private server until you connect to the routing peer that routes traffic to it. You can also confirm that with the `netbird status -d` command. See output from your peer: ``` Nameservers: [192.168.20.1:53] for [anon-cxxx2.domain, anon-gUfys.domain] is Available [10.0.0.1:53] for [.] is Available [172.16.3.200:53, 172.16.3.202:53] for [ad.anon-zffBq.domain] is Available ``` To disable the debug logs you can run: ``` [Environment]::SetEnvironmentVariable("NB_LOG_LEVEL", "info", "Machine") ``` @cleveHEX As we couldn't reproduce the issue, it would be great if you could run the tests we described before with the debug logs. In the meantime, I will close this issue and we can either open a new one or reopen this one to proceed.
saavagebueno commented 2025-11-20 06:04:03 -05:00
Author
Owner
Copy Link

@cleveHEX commented on GitHub (Mar 13, 2025):

@mlsmaycon for me it's completely unrelated to updates/upgrades, my Netbird service sometimes dies 2 times a day without any action from my side, maybe the computer puts itself into sleep mode. I have set the debug mode and next time I encounter this I will attach the log.

@cleveHEX commented on GitHub (Mar 13, 2025): @mlsmaycon for me it's completely unrelated to updates/upgrades, my Netbird service sometimes dies 2 times a day without any action from my side, maybe the computer puts itself into sleep mode. I have set the debug mode and next time I encounter this I will attach the log.
saavagebueno commented 2025-11-20 06:04:03 -05:00
Author
Owner
Copy Link

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

Got it. Then it is better to open a new issue when you reproduce to keep issues in different threads.

@mlsmaycon commented on GitHub (Mar 13, 2025): Got it. Then it is better to open a new issue when you reproduce to keep issues in different threads.
saavagebueno commented 2025-11-20 06:04:03 -05:00
Author
Owner
Copy Link

@tomashora commented on GitHub (Mar 14, 2025):

@mlsmaycon created new issue with debug bundle with log level debug https://github.com/netbirdio/netbird/issues/3503

@tomashora commented on GitHub (Mar 14, 2025): @mlsmaycon created new issue with debug bundle with log level debug https://github.com/netbirdio/netbird/issues/3503
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label triage-needed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1643
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?