[GH-ISSUE #1542] Netbird agent cannot reconnect to signal/management server #2622

Open
opened 2026-08-05 00:48:07 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @gBillal on GitHub (Feb 8, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1542

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). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1542 **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 2026-08-05 00:48:07 -04:00
Sign in to join this conversation.
No Label triage
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2622