Netbird won't connect

[kosinus2pi]

Describe the problem

When NetBird disconnects—typically due to sleep mode or a network change—attempting to bring it back up using netbird up or connect from GUI often fails. Instead of reconnecting, the command hangs for a few minutes and then returns the following: Error: call service up method: rpc error: code = DeadlineExceeded desc = context deadline exceeded

This behavior is occasionally resolved by restarting the NetBird service, but not consistently. In some cases, a full system reboot is required for NetBird to reconnect properly.

To Reproduce

Steps to reproduce the behavior:

Type netbird up or click connect in Netbird GUI

Expected behavior

Netbird connects to overlay network

Are you using NetBird Cloud?

No, self-hosted instance

NetBird version

0.39.2

Is any other VPN software installed?

No

Debug output

To help us resolve the problem, please attach the following debug output

Can't do that, as netbird won't connect. Attached client.log

2025-04-08T15:34:11+02:00 INFO client/internal/engine.go:1664: Network monitor is disabled, not starting
2025-04-08T15:34:11+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:530: closing all peer connections
2025-04-08T15:34:11+02:00 INFO client/internal/connect.go:281: Netbird engine started, the IP is: 100.118.234.50/16
2025-04-08T15:34:11+02:00 INFO client/internal/statemanager/manager.go:412: cleaning up state nftables_state
2025-04-08T15:34:11+02:00 WARN signal/client/grpc.go:143: disconnected from the Signal Exchange due to an error: didn't receive a registration header from the Signal server whille connecting to the streams
2025-04-08T15:34:11+02:00 ERRO signal/client/grpc.go:171: exiting the Signal service connection retry loop due to the unrecoverable error: context canceled
2025-04-08T15:34:11+02:00 INFO client/internal/connect.go:294: ensuring wt0 is removed, Netbird engine context cancelled
2025-04-08T15:34:11+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:336: start to Relay read loop exit
2025-04-08T15:34:11+02:00 INFO client/internal/engine.go:269: Network monitor: stopped
2025-04-08T15:34:11+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:538: waiting for read loop to close
2025-04-08T15:34:11+02:00 INFO client/internal/dns/systemd_linux.go:170: reverting link settings and flushing cache
2025-04-08T15:34:11+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:540: relay connection closed
2025-04-08T15:34:11+02:00 WARN [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:525: relay connection was already marked as not running
2025-04-08T15:34:11+02:00 ERRO management/client/grpc.go:279: failed while getting Management Service public key: rpc error: code = Canceled desc = context canceled
2025-04-08T15:34:11+02:00 WARN management/client/grpc.go:136: exiting the Management service connection retry loop due to the unrecoverable error: context canceled
2025-04-08T15:34:11+02:00 INFO client/internal/routemanager/manager.go:258: Routing cleanup complete
2025-04-08T15:34:12+02:00 INFO client/internal/connect.go:122: starting NetBird client version 0.39.2 on linux/amd64
2025-04-08T15:34:12+02:00 INFO util/net/env_linux.go:70: system supports advanced routing
2025-04-08T15:34:12+02:00 ERRO client/iface/bind/udp_mux_universal.go:97: error while reading packet: shared socked stopped
2025-04-08T15:34:12+02:00 INFO client/iface/iface.go:229: interface wt0 has been removed
2025-04-08T15:34:12+02:00 INFO client/internal/engine.go:320: stopped Netbird Engine
2025-04-08T15:34:12+02:00 INFO client/internal/connect.go:305: stopped NetBird client
2025-04-08T15:34:12+02:00 INFO client/internal/connect.go:255: connecting to the Relay service(s): rels://relay.masked.netbird.io:443, rels://relay-2.masked.netbird.io:443
2025-04-08T15:34:12+02:00 INFO relay/client/picker.go:72: try to connecting to relay server: rels://relay.masked.netbird.io:443
2025-04-08T15:34:12+02:00 INFO relay/client/picker.go:72: try to connecting to relay server: rels://relay-2.masked.netbird.io:443
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:164: create new relay connection: local peerID: uLoBnneWycggJan0g892cnrbAVzHDkj3+PrDEyPIGx8=, local peer hashedID: sha-Vrt85e6D5Mzg5ZLTcQNEH3MAQuDbJf+YcXc7tGgTITk=
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:170: connecting to relay server
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/client.go:164: create new relay connection: local peerID: uLoBnneWycggJan0g892cnrbAVzHDkj3+PrDEyPIGx8=, local peer hashedID: sha-Vrt85e6D5Mzg5ZLTcQNEH3MAQuDbJf+YcXc7tGgTITk=
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/client.go:170: connecting to relay server
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/dialer/race_dialer.go:64: dialing Relay server via quic
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/dialer/race_dialer.go:64: dialing Relay server via quic
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/dialer/race_dialer.go:64: dialing Relay server via WS
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/dialer/race_dialer.go:64: dialing Relay server via WS
2025-04-08T15:34:12+02:00 ERRO relay/client/dialer/quic/quic.go:55: failed to dial to Relay server via QUIC 'relay.masked.netbird.io:443': CRYPTO_ERROR 0x150 (remote): tls: internal error
2025-04-08T15:34:12+02:00 ERRO [relay: rels://relay.masked.netbird.io:443] relay/client/dialer/race_dialer.go:77: failed to dial via quic: CRYPTO_ERROR 0x150 (remote): tls: internal error
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/dialer/race_dialer.go:89: successfully dialed via: WS
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:186: relay connection established
2025-04-08T15:34:12+02:00 INFO relay/client/picker.go:90: connected to Relay server: rels://relay.masked.netbird.io:443
2025-04-08T15:34:12+02:00 INFO relay/client/picker.go:64: chosen home Relay server: rels://relay.masked.netbird.io:443
2025-04-08T15:34:12+02:00 INFO client/iface/wgproxy/ebpf/proxy.go:91: local wg proxy listening on: 3128
2025-04-08T15:34:12+02:00 INFO client/iface/wgproxy/factory_kernel.go:29: WireGuard Proxy Factory will produce eBPF proxy
2025-04-08T15:34:12+02:00 INFO client/internal/routemanager/manager.go:193: Routing setup complete
2025-04-08T15:34:12+02:00 ERRO relay/client/dialer/quic/quic.go:55: failed to dial to Relay server via QUIC 'relay-2.masked.netbird.io:443': CRYPTO_ERROR 0x150 (remote): tls: internal error
2025-04-08T15:34:12+02:00 ERRO [relay: rels://relay-2.masked.netbird.io:443] relay/client/dialer/race_dialer.go:77: failed to dial via quic: CRYPTO_ERROR 0x150 (remote): tls: internal error
2025-04-08T15:34:12+02:00 INFO client/firewall/create_linux.go:73: creating an nftables firewall manager
2025-04-08T15:34:12+02:00 INFO client/internal/dns/host_unix.go:54: System DNS manager discovered: systemd
2025-04-08T15:34:13+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/dialer/race_dialer.go:89: successfully dialed via: WS
2025-04-08T15:34:13+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/client.go:186: relay connection established
2025-04-08T15:34:13+02:00 INFO relay/client/picker.go:90: connected to Relay server: rels://relay-2.masked.netbird.io:443
2025-04-08T15:34:13+02:00 INFO relay/client/picker.go:93: closing unnecessary Relay connection to: rels://relay-2.masked.netbird.io:443
2025-04-08T15:34:13+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/client.go:530: closing all peer connections
2025-04-08T15:34:13+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/client.go:336: start to Relay read loop exit
2025-04-08T15:34:13+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/client.go:538: waiting for read loop to close
2025-04-08T15:34:13+02:00 INFO [relay: rels://relay-2.masked.netbird.io:443] relay/client/client.go:540: relay connection closed
2025-04-08T15:34:13+02:00 WARN [relay: rels://relay-2.masked.netbird.io:443] relay/client/client.go:525: relay connection was already marked as not running

Add any other context about the problem here.

Have you tried these troubleshooting steps?

• Checked for newer NetBird versions - Yes
• Searched for similar issues on GitHub (including closed ones) - Yes
• Restarted the NetBird client - Yes
• Disabled other VPN software - n/a
• Checked firewall settings - Yes

[nazarewk]

seems like your relay might have it's certificate expired:

2025-04-08T15:34:12+02:00 ERRO relay/client/dialer/quic/quic.go:55: failed to dial to Relay server via QUIC 'relay-2.masked.netbird.io:443': CRYPTO_ERROR 0x150 (remote): tls: internal error
2025-04-08T15:34:12+02:00 ERRO [relay: rels://relay-2.masked.netbird.io:443] relay/client/dialer/race_dialer.go:77: failed to dial via quic: CRYPTO_ERROR 0x150 (remote): tls: internal error

Can you make sure the certificate is valid? restarting the relay should help

[nazarewk]

FYI: There are some errors in the logs excerpt, but those seem to be irrelevant.

It could be duplicate of #3503

Could you describe your set up in as much detail as possible so we can try to reproduce it ourselves?

[kosinus2pi]

seems like your relay might have it's certificate expired:

2025-04-08T15:34:12+02:00 ERRO relay/client/dialer/quic/quic.go:55: failed to dial to Relay server via QUIC 'relay-2.masked.netbird.io:443': CRYPTO_ERROR 0x150 (remote): tls: internal error
2025-04-08T15:34:12+02:00 ERRO [relay: rels://relay-2.masked.netbird.io:443] relay/client/dialer/race_dialer.go:77: failed to dial via quic: CRYPTO_ERROR 0x150 (remote): tls: internal error

Can you make sure the certificate is valid? restarting the relay should help

The certificate is valid, it connect with WS, but fails with QUIC.
2025-04-08T15:34:12+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/dialer/race_dialer.go:89: successfully dialed via: WS 2025-04-08T15:34:12+02:00 INFO [relay: rels://relay.masked.netbird.io:443] relay/client/client.go:186: relay connection established

Setup:

• Management server running management, signal, dashboard and nginx in docker (and certbot for cert renewal) behind Cloudflare
• 2 relay servers
• all 3 are on different domain than our Netbird domain

[kosinus2pi]

The issue was caused by the Cloudflare proxy, though the exact reason is unknown, especially considering our setup has been in place well before the problems began. After disabling the proxy, the Netbird client connectivity started functioning as expected.

[nazarewk]

The issue was caused by the Cloudflare proxy, though the exact reason is unknown, especially considering our setup has been in place well before the problems began. After disabling the proxy, the Netbird client connectivity started functioning as expected.

just to chine in, as far as I know the primary (and possibly only) communication mode for clients is GRPC and that might not work at all from behind Cloudflare proxy.

[6leonardo]

netbird client crash i think for a old version of go
SYS_SECCOMP violation on syscall 434 (fatal signal 31)