[GH-ISSUE #4924] Docker containers can't connect to relay server on the same host. #10363

Open
opened 2026-08-05 01:25:37 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @rehcnt on GitHub (Dec 7, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4924

Describe the problem

Docker containers can't connect to relay server on the same host.

To Reproduce

Steps to reproduce the behavior:

  1. Install relay server to the host, it is working fine.
  2. Install docker container for other service (transmission daemon for example).
  3. Make sure that your client uses relay server on the host.
  4. Try to ping transmission.

Expected behavior

Ping to the the transmission succefully started, as it is to the clients on other hosts from this relay.

Are you using NetBird Cloud?

Self-hosted.

NetBird version

0.60.5

Is any other VPN software installed?

Nope

Debug output

from client:

ping trsm-book
PING trsm-book.srv.example.ru (100.122.93.62) 56(84) bytes of data.
From ivan-asrock (100.122.71.229) icmp_seq=1 Destination Host Unreachable
ping: sendmsg: Требуемый ключ недоступен (Required key not available)
From ivan-asrock (100.122.71.229) icmp_seq=2 Destination Host Unreachable
ping: sendmsg: Требуемый ключ недоступен (Required key not available)

from transmission:

2025-12-07T11:50:22Z ERRO shared/relay/client/dialer/ws/ws.go:48: failed to dial to Relay server 'wss://relay.example.ru:33080': failed to WebSocket dial: failed to send handshake request: Get "https://relay.example.ru:33080/relay": context deadline exceeded

2025-12-07T11:50:22Z ERRO [relay: rels://relay.example.ru:33080] shared/relay/client/dialer/race_dialer.go:79: failed to dial via WS: failed to WebSocket dial: failed to send handshake request: Get "https://relay.example.ru:33080/relay": context deadline exceeded

2025-12-07T11:50:22Z ERRO [peer: mCgMZyNKHammn/1hnZGRl64hjt6DN0ii/0l3SB2aDxo=] client/internal/peer/worker_relay.go:73: failed to open connection via Relay: failed to dial to Relay server on any protocol

2025-12-07T11:50:22Z INFO [relay: rels://relay.example.ru:33080] shared/relay/client/client.go:168: create new relay connection: local peerID: RSMSedGhB/HWyUXbNqZozjnqDzjiX6rAzD4DOc/gqFs=, local peer hashedID: sha-sMyvTFWd4DJn6MSCPRuQ8W37w0CiKV8kKagBjt8zoFA=

2025-12-07T11:50:22Z INFO [relay: rels://relay.example.ru:33080] shared/relay/client/client.go:174: connecting to relay server

2025-12-07T11:50:22Z INFO [relay: rels://relay.example.ru:33080] shared/relay/client/dialer/race_dialer.go:66: dialing Relay server via quic

2025-12-07T11:50:22Z INFO [relay: rels://relay.example.ru:33080] shared/relay/client/dialer/race_dialer.go:66: dialing Relay server via WS

2025-12-07T11:50:27Z ERRO shared/relay/client/dialer/quic/quic.go:65: failed to dial to Relay server via QUIC 'relay.example.ru:33080': timeout: no recent network activity

2025-12-07T11:50:27Z ERRO [relay: rels://relay.example.ru:33080] shared/relay/client/dialer/race_dialer.go:79: failed to dial via quic: timeout: no recent network activity

2025-12-07T11:50:41Z INFO [peer: mCgMZyNKHammn/1hnZGRl64hjt6DN0ii/0l3SB2aDxo=] client/internal/peer/conn.go:291: OnRemoteOffer, on status ICE: Disconnected, status Relay: Disconnected

Alternatively, create the file only and attach it here manually:

netbird.debug.2015173219.zip

Additional context

Add any other context about the problem here.

Have you tried these troubleshooting steps?

  • [] Reviewed client troubleshooting (if applicable)
  • [*] Checked for newer NetBird versions
  • [*] Searched for similar issues on GitHub (including closed ones)
  • [ *] Restarted the NetBird client
  • Disabled other VPN software
  • [ *] Checked firewall settings
Originally created by @rehcnt on GitHub (Dec 7, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4924 **Describe the problem** Docker containers can't connect to relay server on the same host. **To Reproduce** Steps to reproduce the behavior: 1. Install relay server to the host, it is working fine. 2. Install docker container for other service (transmission daemon for example). 3. Make sure that your client uses relay server on the host. 4. Try to ping transmission. **Expected behavior** Ping to the the transmission succefully started, as it is to the clients on other hosts from this relay. **Are you using NetBird Cloud?** Self-hosted. **NetBird version** 0.60.5 **Is any other VPN software installed?** Nope **Debug output** from client: ping trsm-book PING trsm-book.srv.example.ru (100.122.93.62) 56(84) bytes of data. From ivan-asrock (100.122.71.229) icmp_seq=1 Destination Host Unreachable ping: sendmsg: Требуемый ключ недоступен (Required key not available) From ivan-asrock (100.122.71.229) icmp_seq=2 Destination Host Unreachable ping: sendmsg: Требуемый ключ недоступен (Required key not available) from transmission: 2025-12-07T11:50:22Z ERRO shared/relay/client/dialer/ws/ws.go:48: failed to dial to Relay server 'wss://relay.example.ru:33080': failed to WebSocket dial: failed to send handshake request: Get "https://relay.example.ru:33080/relay": context deadline exceeded 2025-12-07T11:50:22Z ERRO [relay: rels://relay.example.ru:33080] shared/relay/client/dialer/race_dialer.go:79: failed to dial via WS: failed to WebSocket dial: failed to send handshake request: Get "https://relay.example.ru:33080/relay": context deadline exceeded 2025-12-07T11:50:22Z ERRO [peer: mCgMZyNKHammn/1hnZGRl64hjt6DN0ii/0l3SB2aDxo=] client/internal/peer/worker_relay.go:73: failed to open connection via Relay: failed to dial to Relay server on any protocol 2025-12-07T11:50:22Z INFO [relay: rels://relay.example.ru:33080] shared/relay/client/client.go:168: create new relay connection: local peerID: RSMSedGhB/HWyUXbNqZozjnqDzjiX6rAzD4DOc/gqFs=, local peer hashedID: sha-sMyvTFWd4DJn6MSCPRuQ8W37w0CiKV8kKagBjt8zoFA= 2025-12-07T11:50:22Z INFO [relay: rels://relay.example.ru:33080] shared/relay/client/client.go:174: connecting to relay server 2025-12-07T11:50:22Z INFO [relay: rels://relay.example.ru:33080] shared/relay/client/dialer/race_dialer.go:66: dialing Relay server via quic 2025-12-07T11:50:22Z INFO [relay: rels://relay.example.ru:33080] shared/relay/client/dialer/race_dialer.go:66: dialing Relay server via WS 2025-12-07T11:50:27Z ERRO shared/relay/client/dialer/quic/quic.go:65: failed to dial to Relay server via QUIC 'relay.example.ru:33080': timeout: no recent network activity 2025-12-07T11:50:27Z ERRO [relay: rels://relay.example.ru:33080] shared/relay/client/dialer/race_dialer.go:79: failed to dial via quic: timeout: no recent network activity 2025-12-07T11:50:41Z INFO [peer: mCgMZyNKHammn/1hnZGRl64hjt6DN0ii/0l3SB2aDxo=] client/internal/peer/conn.go:291: OnRemoteOffer, on status ICE: Disconnected, status Relay: Disconnected Alternatively, create the file only and attach it here manually: [netbird.debug.2015173219.zip](https://github.com/user-attachments/files/24015440/netbird.debug.2015173219.zip) **Additional context** Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [*] Checked for newer NetBird versions - [*] Searched for similar issues on GitHub (including closed ones) - [ *] Restarted the NetBird client - [x] Disabled other VPN software - [ *] Checked firewall settings
saavagebueno added the triage-needed label 2026-08-05 01:25:37 -04:00
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10363