2/3 Relays
:~$ sudo docker logs -f netbird-relay
Error response from daemon: No such container: netbird-relay
john@userver:~$ sudo docker logs -f netbird-relay-1
2025-09-18T19:47:23Z INFO relay/cmd/root.go:163: server will be available on: rels://netbird.url.com:33080/relay
2025-09-18T19:47:23Z INFO relay/cmd/root.go:131: running metrics server: :9090/metrics
2025-09-18T19:47:23Z INFO relay/healthcheck/healthcheck.go:76: starting healthcheck server on: http://0.0.0.0:9000/health
2025-09-18T19:47:23Z WARN relay/server/server.go:77: Not starting QUIC listener: valid TLS config is required for QUIC listener
2025-09-18T19:47:23Z INFO relay/server/listener/ws/listener.go:44: WS server listening address: :33080
linux/amd64
Daemon version: 0.57.1
CLI version: 0.57.1
Profile: default
Management: Connected to https://netbird.url.com:443
Signal: Connected to https://netbird.url.com:443
Relays:
[stun:netbird.url.com:3478] is Available
[turn:netbird.url.com:3478?transport=udp] is Available
[rels://netbird.url.com:33080/relay] is Unavailable, reason: relay client not connected
Nameservers:
[1.1.1.1:53, 1.0.0.1:53] for [.] is Available
FQDN: userver.netbird.selfhosted
NetBird IP: 100.66.175.201/16
Interface type: Kernel
Quantum resistance: false
Lazy connection: false
Networks: 0.0.0.0/0
Forwarding rules: 0
Peers count: 1/3 Connected
0 Replies