SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-08-04 19:55:09 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Netbird agent cannot reconnect to signal/management server #613

New Issue
Closed
opened 2025-11-20 05:14:44 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:14:44 -05:00
Owner
Copy Link

Originally created by @gBillal on GitHub (Feb 8, 2024).

Describe the problem

Sometimes the agent disconnect (bad internet connection) from the Signal/management server and fails to reconnect again (sometimes to both Signal/Management, sometimes to one of them)

Expected behavior

The agent should reconnect when connection is stable again.

Are you using NetBird Cloud?

Self-hosted

NetBird version

v0.25.6

NetBird status -d output:

Daemon version: 0.25.6
CLI version: 0.25.6
Management: Connected
Signal: Disconnected, reason: rpc error: code = Unavailable desc = error reading from server: read tcp 192.168.1.36:44242->xxx.xxx.xxx.xxx:443: read: connection timed out
Relays: 0/2 Available
FQDN: xxxx.vpn.xxxx.xx
NetBird IP: 100.105.188.138/16
Interface type: Kernel
Peers count: 0/2 Connected

Another device reports this

Daemon version: 0.25.6
CLI version: 0.25.6
Management: Disconnected, reason: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout
Signal: Connected
Relays: 0/2 Available
FQDN: xxxx.vpn.xxxx.xx
NetBird IP: 100.105.26.217/16
Interface type: Kernel
Peers count: 1/2 Connected

Additional context

The client is running on rpi 4

The client.log reports this

2024-02-07T12:55:27Z INFO client/internal/connect.go:95: starting NetBird client version 0.25.6
2024-02-07T12:55:27Z INFO client/internal/wgproxy/proxy_ebpf.go:79: local wg proxy listening on: 3128
2024-02-07T12:55:27Z INFO signal/client/grpc.go:157: connected to the Signal Service stream
2024-02-07T12:55:27Z INFO client/internal/connect.go:238: Netbird engine started, my IP is: 100.105.188.138/16
2024-02-07T12:55:27Z INFO management/client/grpc.go:143: connected to the Management Service stream
2024-02-07T12:55:27Z INFO client/internal/dns/resolvconf_linux.go:71: added 1 search domains. Search list: [xxxx.xxxx.xx]
2024-02-07T12:55:28Z INFO client/internal/acl/manager.go:52: ACL rules processed in: 3.771617ms, total rules count: 2
2024-02-07T12:55:30Z INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
2024-02-07T13:43:20Z WARN [error: read udp 192.168.1.36:55032->1.1.1.1:53: i/o timeout, upstream: 1.1.1.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream
2024-02-07T13:43:22Z WARN [error: read udp 192.168.1.36:46082->1.0.0.1:53: i/o timeout, upstream: 1.0.0.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream
2024-02-07T13:43:22Z ERRO client/internal/dns/upstream.go:127: all queries to the upstream nameservers failed with timeout
2024-02-07T13:54:24Z INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
2024-02-07T13:55:23Z INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
2024-02-07T14:18:07Z WARN signal/client/grpc.go:170: disconnected from the Signal service but will retry silently. Reason: rpc error: code = Unavailable desc = error reading from server: read tcp 192.168.1.36:44242->167.235.156.149:443: read: connection timed out
2024-02-07T14:18:18Z WARN [error: read udp 192.168.1.36:58867->1.1.1.1:53: i/o timeout, upstream: 1.1.1.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream
2024-02-07T14:18:36Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:38Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:39Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:41Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:42Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:44Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:44Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:45Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:46Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:48Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:49Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:51Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:52Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:53Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:55Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:56Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:57Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:58Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:18:59Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:00Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:01Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:02Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:03Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:05Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:06Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:08Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:09Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:10Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:11Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=
2024-02-07T14:19:13Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY=

This last log repeats forever

For the second device

2024-02-07T09:29:36-06:00 WARN [error: read udp 192.168.8.100:40221->1.1.1.1:53: i/o timeout, upstream: 1.1.1.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream
2024-02-07T09:29:36-06:00 WARN [upstream: 1.1.1.1:53, error: read udp 192.168.8.100:55962->1.1.1.1:53: i/o timeout] client/internal/dns/upstream.go:95: got an error while connecting to upstream
2024-02-07T09:29:38-06:00 WARN [error: read udp 192.168.8.100:58896->1.0.0.1:53: i/o timeout, upstream: 1.0.0.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream
2024-02-07T09:29:38-06:00 ERRO client/internal/dns/upstream.go:127: all queries to the upstream nameservers failed with timeout
2024-02-07T09:29:38-06:00 WARN [error: read udp 192.168.8.100:45893->1.0.0.1:53: i/o timeout, upstream: 1.0.0.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream
2024-02-07T09:29:38-06:00 ERRO client/internal/dns/upstream.go:127: all queries to the upstream nameservers failed with timeout
2024-02-07T12:15:23-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
2024-02-07T18:30:36-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
2024-02-07T18:31:43-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
2024-02-07T18:39:56-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
2024-02-07T18:41:42-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
2024-02-07T18:43:04-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820
Originally created by @gBillal on GitHub (Feb 8, 2024). **Describe the problem** Sometimes the agent disconnect (bad internet connection) from the Signal/management server and fails to reconnect again (sometimes to both Signal/Management, sometimes to one of them) **Expected behavior** The agent should reconnect when connection is stable again. **Are you using NetBird Cloud?** Self-hosted **NetBird version** `v0.25.6` **NetBird status -d output:** ``` Daemon version: 0.25.6 CLI version: 0.25.6 Management: Connected Signal: Disconnected, reason: rpc error: code = Unavailable desc = error reading from server: read tcp 192.168.1.36:44242->xxx.xxx.xxx.xxx:443: read: connection timed out Relays: 0/2 Available FQDN: xxxx.vpn.xxxx.xx NetBird IP: 100.105.188.138/16 Interface type: Kernel Peers count: 0/2 Connected ``` Another device reports this ``` Daemon version: 0.25.6 CLI version: 0.25.6 Management: Disconnected, reason: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout Signal: Connected Relays: 0/2 Available FQDN: xxxx.vpn.xxxx.xx NetBird IP: 100.105.26.217/16 Interface type: Kernel Peers count: 1/2 Connected ``` **Additional context** The client is running on rpi 4 The `client.log` reports this ``` 2024-02-07T12:55:27Z INFO client/internal/connect.go:95: starting NetBird client version 0.25.6 2024-02-07T12:55:27Z INFO client/internal/wgproxy/proxy_ebpf.go:79: local wg proxy listening on: 3128 2024-02-07T12:55:27Z INFO signal/client/grpc.go:157: connected to the Signal Service stream 2024-02-07T12:55:27Z INFO client/internal/connect.go:238: Netbird engine started, my IP is: 100.105.188.138/16 2024-02-07T12:55:27Z INFO management/client/grpc.go:143: connected to the Management Service stream 2024-02-07T12:55:27Z INFO client/internal/dns/resolvconf_linux.go:71: added 1 search domains. Search list: [xxxx.xxxx.xx] 2024-02-07T12:55:28Z INFO client/internal/acl/manager.go:52: ACL rules processed in: 3.771617ms, total rules count: 2 2024-02-07T12:55:30Z INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 2024-02-07T13:43:20Z WARN [error: read udp 192.168.1.36:55032->1.1.1.1:53: i/o timeout, upstream: 1.1.1.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream 2024-02-07T13:43:22Z WARN [error: read udp 192.168.1.36:46082->1.0.0.1:53: i/o timeout, upstream: 1.0.0.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream 2024-02-07T13:43:22Z ERRO client/internal/dns/upstream.go:127: all queries to the upstream nameservers failed with timeout 2024-02-07T13:54:24Z INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 2024-02-07T13:55:23Z INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 2024-02-07T14:18:07Z WARN signal/client/grpc.go:170: disconnected from the Signal service but will retry silently. Reason: rpc error: code = Unavailable desc = error reading from server: read tcp 192.168.1.36:44242->167.235.156.149:443: read: connection timed out 2024-02-07T14:18:18Z WARN [error: read udp 192.168.1.36:58867->1.1.1.1:53: i/o timeout, upstream: 1.1.1.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream 2024-02-07T14:18:36Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:38Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:39Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:41Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:42Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:44Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:44Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:45Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:46Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:48Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:49Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:51Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:52Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:53Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:55Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:56Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:57Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:58Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:18:59Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:00Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:01Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:02Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:03Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:05Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:06Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:08Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:09Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:10Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:11Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= 2024-02-07T14:19:13Z INFO client/internal/engine.go:820: signal client isn't ready, skipping connection attempt lSP+cFmA1h5YqZBFaivugk+hALoWphK/VZfLffBIOFY= ``` This last log repeats forever For the second device ``` 2024-02-07T09:29:36-06:00 WARN [error: read udp 192.168.8.100:40221->1.1.1.1:53: i/o timeout, upstream: 1.1.1.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream 2024-02-07T09:29:36-06:00 WARN [upstream: 1.1.1.1:53, error: read udp 192.168.8.100:55962->1.1.1.1:53: i/o timeout] client/internal/dns/upstream.go:95: got an error while connecting to upstream 2024-02-07T09:29:38-06:00 WARN [error: read udp 192.168.8.100:58896->1.0.0.1:53: i/o timeout, upstream: 1.0.0.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream 2024-02-07T09:29:38-06:00 ERRO client/internal/dns/upstream.go:127: all queries to the upstream nameservers failed with timeout 2024-02-07T09:29:38-06:00 WARN [error: read udp 192.168.8.100:45893->1.0.0.1:53: i/o timeout, upstream: 1.0.0.1:53] client/internal/dns/upstream.go:95: got an error while connecting to upstream 2024-02-07T09:29:38-06:00 ERRO client/internal/dns/upstream.go:127: all queries to the upstream nameservers failed with timeout 2024-02-07T12:15:23-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 2024-02-07T18:30:36-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 2024-02-07T18:31:43-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 2024-02-07T18:39:56-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 2024-02-07T18:41:42-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 2024-02-07T18:43:04-06:00 INFO client/internal/peer/conn.go:357: connected to peer I7LopCdHw08ogCVp8ig2+EHeQy+6SxmlfKbwCT0xGm4=, endpoint address: xx.xx.xx.xx:51820 ```
saavagebueno added the triage label 2025-11-20 05:14:44 -05:00
saavagebueno commented 2025-11-20 05:14:45 -05:00
Author
Owner
Copy Link

@gBillal commented on GitHub (Feb 13, 2024):

Mis-configuration on our side. We used the same domain name as our management server for the peers which caused the management domain name to be unresolved.

@gBillal commented on GitHub (Feb 13, 2024): Mis-configuration on our side. We used the same domain name as our management server for the peers which caused the management domain name to be unresolved.
saavagebueno commented 2025-11-20 05:14:45 -05:00
Author
Owner
Copy Link

@TjerkvGerwen commented on GitHub (Mar 22, 2024):

Hey i have the same issue and not a lot of experience what do you mean with we used the same domain name as our management server for the peers?

-------LOG--------
2024-03-22T20:51:21+01:00 WARN signal/client/grpc.go:150: disconnected from the Signal Exchange due to an error: rpc error: code = Unavailable desc = connection error: desc = "error reading from server: read tcp 192.168.100.2:53596->Public IP server:443: wsarecv: An established connection was aborted by the software in your host machine."
2024-03-22T20:51:22+01:00 INFO client/internal/engine.go:836: signal client isn't ready, skipping connection attempt +OjkQE3WAsKUapYclh+syv52L2Fwjx+JZg8/S2/zihE=
2024-03-22T20:51:51+01:00 INFO client/internal/engine.go:836: signal client isn't ready, skipping connection attempt +OjkQE3WAsKUapYclh+syv52L2Fwjx+JZg8/S2/zihE=

@TjerkvGerwen commented on GitHub (Mar 22, 2024): Hey i have the same issue and not a lot of experience what do you mean with we used the same domain name as our management server for the peers? -------LOG-------- 2024-03-22T20:51:21+01:00 WARN signal/client/grpc.go:150: disconnected from the Signal Exchange due to an error: rpc error: code = Unavailable desc = connection error: desc = "error reading from server: read tcp 192.168.100.2:53596->Public IP server:443: wsarecv: An established connection was aborted by the software in your host machine." 2024-03-22T20:51:22+01:00 INFO client/internal/engine.go:836: signal client isn't ready, skipping connection attempt +OjkQE3WAsKUapYclh+syv52L2Fwjx+JZg8/S2/zihE= 2024-03-22T20:51:51+01:00 INFO client/internal/engine.go:836: signal client isn't ready, skipping connection attempt +OjkQE3WAsKUapYclh+syv52L2Fwjx+JZg8/S2/zihE=
saavagebueno commented 2025-11-20 05:14:45 -05:00
Author
Owner
Copy Link

@gBillal commented on GitHub (Mar 22, 2024):

We self hosted netbird and let's say that we used vpn.example.io as our domain name for the management server. We also used the same domain for our peers, so when peers connect to the management server they are given domain names like: peer1.vpn.example.io, peer2.vpn.example.io, ...etc. However when a peer disconnect, it can no longer resolve the vpn.example.io so it fails to reconnect again.

What we did is change the domain name given to the peers to netbird.example in docker-compose.yml file

...
  management:
    image: netbirdio/management:latest
    restart: unless-stopped
    networks: [netbird]
    depends_on:
      - dashboard
    volumes:
      - ./netbird-mgmt:/var/lib/netbird
      - ./management.json:/etc/netbird/management.json
    command: [
      "--port", "80",
      "--log-file", "console",
      "--log-level", "info",
      "--disable-anonymous-metrics=false",
      "--single-account-mode-domain=vpn.example.io",
      "--dns-domain=netbird.example" # <-- we changed this value
...
@gBillal commented on GitHub (Mar 22, 2024): We self hosted netbird and let's say that we used `vpn.example.io` as our domain name for the management server. We also used the same domain for our peers, so when peers connect to the management server they are given domain names like: `peer1.vpn.example.io`, `peer2.vpn.example.io`, ...etc. However when a peer disconnect, it can no longer resolve the `vpn.example.io` so it fails to reconnect again. What we did is change the domain name given to the peers to `netbird.example` in `docker-compose.yml` file ```yaml ... management: image: netbirdio/management:latest restart: unless-stopped networks: [netbird] depends_on: - dashboard volumes: - ./netbird-mgmt:/var/lib/netbird - ./management.json:/etc/netbird/management.json command: [ "--port", "80", "--log-file", "console", "--log-level", "info", "--disable-anonymous-metrics=false", "--single-account-mode-domain=vpn.example.io", "--dns-domain=netbird.example" # <-- we changed this value ... ```
saavagebueno commented 2025-11-20 05:14:45 -05:00
Author
Owner
Copy Link

@TjerkvGerwen commented on GitHub (Mar 23, 2024):

Thank you for your clear answer! 🤗

@TjerkvGerwen commented on GitHub (Mar 23, 2024): Thank you for your clear answer! 🤗
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
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#613
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?