SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-27 16:32:34 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Windows10下Netbird Service会闪退 #769

New Issue
Closed
opened 2025-11-20 05:17:10 -05:00 by saavagebueno · 15 comments
saavagebueno commented 2025-11-20 05:17:10 -05:00
Owner
Copy Link

Originally created by @Seacity976 on GitHub (Apr 3, 2024).

首先，在C:\ProgramData\Netbird目录下的日志文件client.log并没有记录到任何报错，大概在运行了1个多小时后，似乎就是莫名其妙的闪退。
image
然后托盘里面的软件disconnect再也没有反应，网络连接里面的wt0也消失了，尝试过将wt0改成seacity0后现象还是会有。必须要调用netbird service start后才能再用。
这是日志的最后几行
image

Originally created by @Seacity976 on GitHub (Apr 3, 2024). 首先，在C:\ProgramData\Netbird目录下的日志文件client.log并没有记录到任何报错，大概在运行了1个多小时后，似乎就是莫名其妙的闪退。 ![image](https://github.com/netbirdio/netbird/assets/165882530/4fc2da80-dc89-4f32-81aa-b1f25c921cba) 然后托盘里面的软件disconnect再也没有反应，网络连接里面的wt0也消失了，尝试过将wt0改成seacity0后现象还是会有。必须要调用netbird service start后才能再用。 这是日志的最后几行 ![image](https://github.com/netbirdio/netbird/assets/165882530/2528c34b-838d-4b6c-bab6-0ca26c211768)
saavagebueno added the bugclientwaiting-feedbackwindowsroutes labels 2025-11-20 05:17:10 -05:00
saavagebueno commented 2025-11-20 05:17:11 -05:00
Author
Owner
Copy Link

@Seacity976 commented on GitHub (Apr 3, 2024):

顺带一提，Windows下用的是最新的0.26.7版本

@Seacity976 commented on GitHub (Apr 3, 2024): 顺带一提，Windows下用的是最新的0.26.7版本
saavagebueno commented 2025-11-20 05:17:11 -05:00
Author
Owner
Copy Link

@bcmmbaga commented on GitHub (Apr 3, 2024):

Hello @Seacity976, could you please share the log files and the output of netbird status -d?

@bcmmbaga commented on GitHub (Apr 3, 2024): Hello @Seacity976, could you please share the log files and the output of `netbird status -d`?
saavagebueno commented 2025-11-20 05:17:12 -05:00
Author
Owner
Copy Link

@Seacity976 commented on GitHub (Apr 3, 2024):

你好@Seacity976，您能分享一下日志文件和输出吗netbird status -d？
你好，输出这个，在我尝试netbird service start后，又可以短暂工作1小时，然后服务又停止了
image
Error: failed to connect to daemon error: context deadline exceeded
If the daemon is not running please run:
netbird service install
netbird service start

@Seacity976 commented on GitHub (Apr 3, 2024): > 你好@Seacity976，您能分享一下日志文件和输出吗`netbird status -d`？ 你好，输出这个，在我尝试netbird service start后，又可以短暂工作1小时，然后服务又停止了 ![image](https://github.com/netbirdio/netbird/assets/165882530/062f9985-d71a-4ed3-960f-5f97dd4bcab0) Error: failed to connect to daemon error: context deadline exceeded If the daemon is not running please run: netbird service install netbird service start
saavagebueno commented 2025-11-20 05:17:12 -05:00
Author
Owner
Copy Link

@Seacity976 commented on GitHub (Apr 3, 2024):

你好@Seacity976，您能分享一下日志文件和输出吗netbird status -d？

日志文件最后几行，是一个小时前的了
image

@Seacity976 commented on GitHub (Apr 3, 2024): > 你好@Seacity976，您能分享一下日志文件和输出吗`netbird status -d`？ 日志文件最后几行，是一个小时前的了 ![image](https://github.com/netbirdio/netbird/assets/165882530/d0e5e6a7-e08e-4446-b130-b9f658201901)
saavagebueno commented 2025-11-20 05:17:12 -05:00
Author
Owner
Copy Link

@bcmmbaga commented on GitHub (Apr 3, 2024):

Please share the entire log file and not screenshots. You can mask any sensitive information such as IP addresses, domains, etc

@bcmmbaga commented on GitHub (Apr 3, 2024): Please share the entire log file and not screenshots. You can mask any sensitive information such as IP addresses, domains, etc
saavagebueno commented 2025-11-20 05:17:12 -05:00
Author
Owner
Copy Link

@Seacity976 commented on GitHub (Apr 3, 2024):

请分享整个日志文件，而不是屏幕截图。您可以屏蔽任何敏感信息，例如 IP 地址、域等

好的，我删掉了一些ip之类的，日志如下：
2024-04-03T13:53:16+08:00 INFO client/cmd/service_controller.go:24: starting Netbird service
2024-04-03T13:53:16+08:00 INFO client/cmd/service_controller.go:64: started daemon server: 127.0.0.1:41731
2024-04-03T13:53:16+08:00 INFO client/internal/connect.go:96: starting NetBird client version 0.26.7
2024-04-03T13:53:19+08:00 INFO client/internal/routemanager/manager.go:76: Routing setup complete
2024-04-03T13:53:20+08:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream
2024-04-03T13:53:20+08:00 INFO client/internal/connect.go:239: Netbird engine started, my IP is: x.x.x.x/16
2024-04-03T13:53:20+08:00 INFO management/client/grpc.go:147: connected to the Management Service stream
2024-04-03T13:53:20+08:00 WARN client/internal/engine.go:498: running SSH server is not permitted
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:20+08:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.netbird.cloud]
2024-04-03T13:53:20+08:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.cloud]
2024-04-03T13:53:20+08:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 0s, total rules count: 2
2024-04-03T13:53:23+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:49961
2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxx with peer with score 2 for network 172.31.23.0/24
2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxx with peer with score 2 for network 192.168.110.0/24
2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer with score 2 for network 172.31.21.0/24
2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxx with peer with score 2 for network 192.168.0.0/18
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820
2024-04-03T13:53:24+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450
2024-04-03T13:53:24+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer with score 2 for network 172.31.25.0/24
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.21.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.23.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.110.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.25.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.100.0/24: remove route: get peer state: peer not found
2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.0.0/18: remove route: get peer state: peer not found
2024-04-03T13:53:27+08:00 INFO client/internal/routemanager/manager.go:98: Routing cleanup complete
2024-04-03T13:53:27+08:00 INFO client/internal/engine.go:220: stopped Netbird Engine
2024-04-03T13:53:27+08:00 INFO client/internal/connect.go:253: stopped NetBird client
2024-04-03T13:53:53+08:00 INFO client/internal/connect.go:96: starting NetBird client version 0.26.7
2024-04-03T13:53:55+08:00 INFO client/internal/routemanager/manager.go:76: Routing setup complete
2024-04-03T13:53:56+08:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream
2024-04-03T13:53:56+08:00 INFO client/internal/connect.go:239: Netbird engine started, my IP is: x.x.x.x/16
2024-04-03T13:53:57+08:00 INFO management/client/grpc.go:147: connected to the Management Service stream
2024-04-03T13:53:57+08:00 WARN client/internal/engine.go:498: running SSH server is not permitted
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T13:53:57+08:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.netbird.cloud]
2024-04-03T13:53:57+08:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.cloud]
2024-04-03T13:53:57+08:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 0s, total rules count: 2
2024-04-03T13:54:00+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820
2024-04-03T13:54:00+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450
2024-04-03T13:54:00+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxx with peer with score 2 for network 172.31.25.0/24
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:49961
2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 192.168.110.0/24
2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 192.168.0.0/18
2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 172.31.21.0/24
2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 172.31.23.0/24
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:45+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected
2024-04-03T14:52:48+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820
2024-04-03T14:52:48+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5vub3xxxxxxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:53+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T14:52:55+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450
2024-04-03T14:52:55+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5vub3xxxxxxxxxxxx with peer with score 2 for network 172.31.25.0/24
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix
2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected
2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected

@Seacity976 commented on GitHub (Apr 3, 2024): > 请分享整个日志文件，而不是屏幕截图。您可以屏蔽任何敏感信息，例如 IP 地址、域等 好的，我删掉了一些ip之类的，日志如下： 2024-04-03T13:53:16+08:00 INFO client/cmd/service_controller.go:24: starting Netbird service 2024-04-03T13:53:16+08:00 INFO client/cmd/service_controller.go:64: started daemon server: 127.0.0.1:41731 2024-04-03T13:53:16+08:00 INFO client/internal/connect.go:96: starting NetBird client version 0.26.7 2024-04-03T13:53:19+08:00 INFO client/internal/routemanager/manager.go:76: Routing setup complete 2024-04-03T13:53:20+08:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream 2024-04-03T13:53:20+08:00 INFO client/internal/connect.go:239: Netbird engine started, my IP is: x.x.x.x/16 2024-04-03T13:53:20+08:00 INFO management/client/grpc.go:147: connected to the Management Service stream 2024-04-03T13:53:20+08:00 WARN client/internal/engine.go:498: running SSH server is not permitted 2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected 2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:20+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:20+08:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.netbird.cloud] 2024-04-03T13:53:20+08:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.cloud] 2024-04-03T13:53:20+08:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 0s, total rules count: 2 2024-04-03T13:53:23+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:49961 2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxx with peer with score 2 for network 172.31.23.0/24 2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxx with peer with score 2 for network 192.168.110.0/24 2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer with score 2 for network 172.31.21.0/24 2024-04-03T13:53:23+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxx with peer with score 2 for network 192.168.0.0/18 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:23+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820 2024-04-03T13:53:24+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450 2024-04-03T13:53:24+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer with score 2 for network 172.31.25.0/24 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:24+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.21.0/24: remove route: get peer state: peer not found 2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.23.0/24: remove route: get peer state: peer not found 2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.110.0/24: remove route: get peer state: peer not found 2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 172.31.25.0/24: remove route: get peer state: peer not found 2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.100.0/24: remove route: get peer state: peer not found 2024-04-03T13:53:26+08:00 ERRO client/internal/routemanager/client.go:299: Couldn't remove route from peer and system for network 192.168.0.0/18: remove route: get peer state: peer not found 2024-04-03T13:53:27+08:00 INFO client/internal/routemanager/manager.go:98: Routing cleanup complete 2024-04-03T13:53:27+08:00 INFO client/internal/engine.go:220: stopped Netbird Engine 2024-04-03T13:53:27+08:00 INFO client/internal/connect.go:253: stopped NetBird client 2024-04-03T13:53:53+08:00 INFO client/internal/connect.go:96: starting NetBird client version 0.26.7 2024-04-03T13:53:55+08:00 INFO client/internal/routemanager/manager.go:76: Routing setup complete 2024-04-03T13:53:56+08:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream 2024-04-03T13:53:56+08:00 INFO client/internal/connect.go:239: Netbird engine started, my IP is: x.x.x.x/16 2024-04-03T13:53:57+08:00 INFO management/client/grpc.go:147: connected to the Management Service stream 2024-04-03T13:53:57+08:00 WARN client/internal/engine.go:498: running SSH server is not permitted 2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected 2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:57+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T13:53:57+08:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.netbird.cloud] 2024-04-03T13:53:57+08:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.cloud] 2024-04-03T13:53:57+08:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 0s, total rules count: 2 2024-04-03T13:54:00+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820 2024-04-03T13:54:00+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450 2024-04-03T13:54:00+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxx with peer with score 2 for network 172.31.25.0/24 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:00+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:49961 2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 192.168.110.0/24 2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 192.168.0.0/18 2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 172.31.21.0/24 2024-04-03T13:54:01+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxx with peer with score 2 for network 172.31.23.0/24 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T13:54:01+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:45+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [+fL5l8=] are currently connected 2024-04-03T14:52:48+08:00 INFO client/internal/peer/conn.go:379: connected to peer +fL5l8=, endpoint address: x.x.x.x:51820 2024-04-03T14:52:48+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5vub3xxxxxxxxxxxx with peer +fL5l8= with score 2 for network 192.168.100.0/24 2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:48+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:53+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T14:52:55+08:00 INFO client/internal/peer/conn.go:379: connected to peer , endpoint address: x.x.x.x:16450 2024-04-03T14:52:55+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5vub3xxxxxxxxxxxx with peer with score 2 for network 172.31.25.0/24 2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 0.0.0.0/0, skipping this prefix 2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:52:55+08:00 WARN client/internal/routemanager/manager.go:213: This agent version: 0.26.7, doesn't support default routes, received 224.0.0.0/4, skipping this prefix 2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [] are currently connected 2024-04-03T14:53:02+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [] are currently connected
saavagebueno commented 2025-11-20 05:17:12 -05:00
Author
Owner
Copy Link

@bcmmbaga commented on GitHub (Apr 3, 2024):

Did this happen after upgrading to v0.26.7?

@bcmmbaga commented on GitHub (Apr 3, 2024): Did this happen after upgrading to v0.26.7?
saavagebueno commented 2025-11-20 05:17:12 -05:00
Author
Owner
Copy Link

@Seacity976 commented on GitHub (Apr 3, 2024):

Did this happen after upgrading to v0.26.7?

0.26.6也会，正是如此，我升级到0.6.27，问题还是存在

@Seacity976 commented on GitHub (Apr 3, 2024): > Did this happen after upgrading to v0.26.7? 0.26.6也会，正是如此，我升级到0.6.27，问题还是存在
saavagebueno commented 2025-11-20 05:17:13 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Apr 4, 2024):

The errors are harmless, this should be fixed with 0.27.0, can you test with that version?

@lixmal commented on GitHub (Apr 4, 2024): The errors are harmless, this should be fixed with `0.27.0`, can you test with that version?
saavagebueno commented 2025-11-20 05:17:13 -05:00
Author
Owner
Copy Link

@Seacity976 commented on GitHub (Apr 4, 2024):

The errors are harmless, this should be fixed with 0.27.0, can you test with that version?

刚试了0.27.0也会，netbird status -d输出如下：
Error: failed to connect to daemon error: context deadline exceeded
If the daemon is not running please run:
netbird service install
netbird service start
服务是自动崩掉了
image
托盘里面Netbird程序还在
image

这个是最新的Client.log
2024-04-04T16:44:17+08:00 INFO client/cmd/service_controller.go:24: starting Netbird service
2024-04-04T16:44:17+08:00 INFO client/cmd/service_controller.go:64: started daemon server: 127.0.0.1:41731
2024-04-04T16:44:17+08:00 INFO client/internal/connect.go:96: starting NetBird client version 0.27.0
2024-04-04T16:44:17+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:18+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:19+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:21+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:25+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:27+08:00 ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded
2024-04-04T16:44:27+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:28+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:29+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:32+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:36+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:37+08:00 ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded
2024-04-04T16:44:37+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:38+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:40+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:43+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:47+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:47+08:00 ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded
2024-04-04T16:44:52+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:53+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:55+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:44:57+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host
2024-04-04T16:45:03+08:00 WARN client/internal/routemanager/systemops.go:81: Failed to get route for ::: Element not found.
2024-04-04T16:45:04+08:00 INFO client/internal/routemanager/manager.go:83: Routing setup complete
2024-04-04T16:45:05+08:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream
2024-04-04T16:45:05+08:00 INFO client/internal/connect.go:239: Netbird engine started, my IP is: xxx.xxx.xxx.xxx/16
2024-04-04T16:45:05+08:00 INFO management/client/grpc.go:147: connected to the Management Service stream
2024-04-04T16:45:06+08:00 WARN client/internal/engine.go:507: running SSH server is not permitted
2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/cXU=] are currently connected
2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
2024-04-04T16:45:06+08:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.netbird.cloud]
2024-04-04T16:45:06+08:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.cloud]
2024-04-04T16:45:06+08:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 0s, total rules count: 2
2024-04-04T16:45:09+08:00 INFO client/internal/peer/conn.go:387: connected to peer xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx=, endpoint address: xxx.xxx.xxxx.xxx:51820
2024-04-04T16:45:09+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5mmarl0ubs73dpghj0 with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 192.168.100.0/24
2024-04-04T16:45:10+08:00 INFO client/internal/peer/conn.go:387: connected to peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=, endpoint address: 14.221.118.148:48669
2024-04-04T16:45:10+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxxxxxxxxxxxxxxxxxx with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 192.168.0.0/18
2024-04-04T16:45:10+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxxxxxxxxxxxxxxxxxx with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 172.31.21.0/24
2024-04-04T16:45:10+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxxxxxxxxxxxxxxxxxx with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 192.168.110.0/24
2024-04-04T16:45:11+08:00 INFO client/internal/peer/conn.go:387: connected to peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/cXU=, endpoint address: xxx.xxx.xxx.xxx:25582
2024-04-04T16:45:11+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxxxxxxxxxxxxxxxxxx with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/cXU= with score 2 for network 172.31.23.0/24
2024-04-04T16:45:12+08:00 INFO client/internal/peer/conn.go:387: connected to peer //xxxxxxxxxxxxxxxxxxxxxxxxxxx=, endpoint address: xxx.xxx.xxx.xxx:16450
2024-04-04T16:45:12+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5vub3l0ubs73dpgr0g with peer /xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 172.31.25.0/24
2024-04-04T16:47:07+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
2024-04-04T16:47:18+08:00 INFO client/internal/peer/conn.go:387: connected to peer xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx=, endpoint address: xxx.xxx.xxx.xxx:51820
2024-04-04T16:47:18+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer xxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 192.168.100.0/24
2024-04-04T17:45:44+08:00 INFO client/internal/engine.go:854: signal client isn't ready, skipping connection attempt xxxxxxxx/xxxxxxxx=
2024-04-04T17:50:28+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
2024-04-04T17:50:28+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
2024-04-04T17:50:28+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected

@Seacity976 commented on GitHub (Apr 4, 2024): > The errors are harmless, this should be fixed with `0.27.0`, can you test with that version? 刚试了0.27.0也会，netbird status -d输出如下： Error: failed to connect to daemon error: context deadline exceeded If the daemon is not running please run: netbird service install netbird service start 服务是自动崩掉了 ![image](https://github.com/netbirdio/netbird/assets/165882530/e9425658-6402-4b35-bb4c-6a184e397f1c) 托盘里面Netbird程序还在 ![image](https://github.com/netbirdio/netbird/assets/165882530/dfc2d921-9dfb-4152-8e2e-5934d6045ecb) 这个是最新的Client.log 2024-04-04T16:44:17+08:00 INFO client/cmd/service_controller.go:24: starting Netbird service 2024-04-04T16:44:17+08:00 INFO client/cmd/service_controller.go:64: started daemon server: 127.0.0.1:41731 2024-04-04T16:44:17+08:00 INFO client/internal/connect.go:96: starting NetBird client version 0.27.0 2024-04-04T16:44:17+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:18+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:19+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:21+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:25+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:27+08:00 ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-04-04T16:44:27+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:28+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:29+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:32+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:36+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:37+08:00 ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-04-04T16:44:37+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:38+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:40+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:43+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:47+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:47+08:00 ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-04-04T16:44:52+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:53+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:55+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:44:57+08:00 ERRO util/grpc/dialer.go:17: Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 2024-04-04T16:45:03+08:00 WARN client/internal/routemanager/systemops.go:81: Failed to get route for ::: Element not found. 2024-04-04T16:45:04+08:00 INFO client/internal/routemanager/manager.go:83: Routing setup complete 2024-04-04T16:45:05+08:00 INFO signal/client/grpc.go:158: connected to the Signal Service stream 2024-04-04T16:45:05+08:00 INFO client/internal/connect.go:239: Netbird engine started, my IP is: xxx.xxx.xxx.xxx/16 2024-04-04T16:45:05+08:00 INFO management/client/grpc.go:147: connected to the Management Service stream 2024-04-04T16:45:06+08:00 WARN client/internal/engine.go:507: running SSH server is not permitted 2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.25.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected 2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected 2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected 2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected 2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.23.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/cXU=] are currently connected 2024-04-04T16:45:06+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected 2024-04-04T16:45:06+08:00 INFO client/internal/dns/host_windows.go:149: added 1 match domains to the state. Domain list: [.netbird.cloud] 2024-04-04T16:45:06+08:00 INFO client/internal/dns/host_windows.go:176: updated the search domains in the registry with 1 domains. Domain list: [netbird.cloud] 2024-04-04T16:45:06+08:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 0s, total rules count: 2 2024-04-04T16:45:09+08:00 INFO client/internal/peer/conn.go:387: connected to peer xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx=, endpoint address: xxx.xxx.xxxx.xxx:51820 2024-04-04T16:45:09+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5mmarl0ubs73dpghj0 with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 192.168.100.0/24 2024-04-04T16:45:10+08:00 INFO client/internal/peer/conn.go:387: connected to peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=, endpoint address: 14.221.118.148:48669 2024-04-04T16:45:10+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxxxxxxxxxxxxxxxxxx with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 192.168.0.0/18 2024-04-04T16:45:10+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxxxxxxxxxxxxxxxxxx with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 172.31.21.0/24 2024-04-04T16:45:10+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxxxxxxxxxxxxxxxxxx with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 192.168.110.0/24 2024-04-04T16:45:11+08:00 INFO client/internal/peer/conn.go:387: connected to peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/cXU=, endpoint address: xxx.xxx.xxx.xxx:25582 2024-04-04T16:45:11+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxxxxxxxxxxxxxxxxxxxxx with peer xxxxxxxxxxxxxxxxxxxxxxxxxxx/cXU= with score 2 for network 172.31.23.0/24 2024-04-04T16:45:12+08:00 INFO client/internal/peer/conn.go:387: connected to peer //xxxxxxxxxxxxxxxxxxxxxxxxxxx=, endpoint address: xxx.xxx.xxx.xxx:16450 2024-04-04T16:45:12+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is co5vub3l0ubs73dpgr0g with peer /xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 172.31.25.0/24 2024-04-04T16:47:07+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.100.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected 2024-04-04T16:47:18+08:00 INFO client/internal/peer/conn.go:387: connected to peer xxxxxxxxxxxxxxxxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx=, endpoint address: xxx.xxx.xxx.xxx:51820 2024-04-04T16:47:18+08:00 INFO client/internal/routemanager/client.go:137: new chosen route is xxxxxxxx with peer xxxxxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxx= with score 2 for network 192.168.100.0/24 2024-04-04T17:45:44+08:00 INFO client/internal/engine.go:854: signal client isn't ready, skipping connection attempt xxxxxxxx/xxxxxxxx= 2024-04-04T17:50:28+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.0.0/18 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected 2024-04-04T17:50:28+08:00 WARN client/internal/routemanager/client.go:134: the network 172.31.21.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected 2024-04-04T17:50:28+08:00 WARN client/internal/routemanager/client.go:134: the network 192.168.110.0/24 has not been assigned a routing peer as no peers from the list [xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx=] are currently connected
saavagebueno commented 2025-11-20 05:17:13 -05:00
Author
Owner
Copy Link

@jiangslee commented on GitHub (Apr 4, 2024):

Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host

你在用官方saas，看着像是DNS被运营商污染了。。

@jiangslee commented on GitHub (Apr 4, 2024): > Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host 你在用官方saas，看着像是DNS被运营商污染了。。
saavagebueno commented 2025-11-20 05:17:13 -05:00
Author
Owner
Copy Link

@Seacity976 commented on GitHub (Apr 4, 2024):

Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host

你在用官方saas，看着像是DNS被运营商污染了。。

还真别说，我改成下面这样子后，就是用谷歌DNS后，已经一个小时了，目前还是正常的，我再观察下
image

@Seacity976 commented on GitHub (Apr 4, 2024): > > Failed to dial: dial: dial tcp: lookup api.netbird.io: no such host > > 你在用官方saas，看着像是DNS被运营商污染了。。 还真别说，我改成下面这样子后，就是用谷歌DNS后，已经一个小时了，目前还是正常的，我再观察下 ![image](https://github.com/netbirdio/netbird/assets/165882530/d5d3b9f0-66e1-4e44-8439-7711ac56582e)
saavagebueno commented 2025-11-20 05:17:13 -05:00
Author
Owner
Copy Link

@Seacity976 commented on GitHub (Apr 4, 2024):

Did this happen after upgrading to v0.26.7?

最后我在https://app.netbird.io/dns/settings，下禁用了windows10的DNS管理，目前跑了很久，没遇到服务挂掉的现象。感觉像是DNS污染后，程序异常闪退了。

@Seacity976 commented on GitHub (Apr 4, 2024): > Did this happen after upgrading to v0.26.7? 最后我在https://app.netbird.io/dns/settings，下禁用了windows10的DNS管理，目前跑了很久，没遇到服务挂掉的现象。感觉像是DNS污染后，程序异常闪退了。
saavagebueno commented 2025-11-20 05:17:13 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 23, 2025):

@Seacity976 Was your problem resolved (and we can close the issue) or is it still happening on the latest NetBird version?

@nazarewk commented on GitHub (Apr 23, 2025): @Seacity976 Was your problem resolved (and we can close the issue) or is it still happening on the latest NetBird version?
saavagebueno commented 2025-11-20 05:17:14 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 1, 2025):

closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.

@mlsmaycon commented on GitHub (Jun 1, 2025): closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.
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 bug client routes waiting-feedback windows
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#769
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?