You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
netbird status gives: reason: relay client not connected
I'm using my own selfhosted netbird server.
To Reproduce
Steps to reproduce the behavior:
Start traefik
Up netbird compose
Try to connect netbird server from cli on desktop
See error: [rel://netbird.domain.com:33080] is Unavailable, reason: relay client not connected
When I tail the "/var/log/netbird/client.log" file: I see:
2025-01-03T00:27:20+03:00 INFO [relay: rel://netbird.domain.com:33080] relay/client/client.go:171: connecting to relay server
2025-01-03T00:27:45+03:00 ERRO relay/client/dialer/ws/ws.go:36: failed to dial to Relay server 'ws://netbird.domain.com:33080': failed to WebSocket dial: failed to send handshake request: Get "http://netbird.domain.com:33080/relay": d.Dialer.DialContext: dial tcp 92.113.26.143:33080: connect: connection timed out
2025-01-03T00:27:50+03:00 ERRO client/internal/connect.go:249: failed to connect to any relay server: context deadline exceeded
2025-01-03T00:27:50+03:00 INFO relay/client/guard.go:68: try to pick up a new Relay server
2025-01-03T00:27:50+03:00 INFO relay/client/picker.go:72: try to connecting to relay server: rel://netbird.domain.com:33080
2025-01-03T00:27:50+03:00 INFO [relay: rel://netbird.domain.com:33080] relay/client/client.go:165: create new relay connection: local peerID: MfThRZtJfCAzzPvrLMfkjGkY1MNRCq15kejfET54RHw=, local peer hashedID: sha-9J7vtUU2mg/gV75vQ+mS1daMJJz0qj+6xnwGL5GhHbk=
Expected behavior
I hope relays' result should be 3/3 connected when I typed "netbird status -d"
Are you using NetBird Cloud?
Netbird Selfhosted
NetBird version
0.35.1
NetBird status -dA output:
Peers detail:
OS: linux/amd64
Daemon version: 0.35.1
CLI version: 0.35.1
Management: Connected to https://netbird.anon-paBa5.domain:443
Signal: Connected to https://netbird.anon-paBa5.domain:80
Relays:
[stun:netbird.anon-paBa5.domain:3478] is Available
[turn:netbird.anon-paBa5.domain:3478?transport=udp] is Available
[rel://netbird.anon-paBa5.domain:33080] is Unavailable, reason: relay client not connected
Nameservers:
FQDN: orion.netbird.selfhosted
NetBird IP: 100.72.198.15/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Networks: -
Peers count: 0/0 Connected
Do you face any (non-mobile) client issues?
.....
Screenshots
....
Additional context
....
The text was updated successfully, but these errors were encountered:
You need to add this section to docker-compose.yml.tmpl.traefik too:
`
Relay
relay:
image: netbirdio/relay:$NETBIRD_RELAY_TAG
restart: unless-stopped
environment:
- NB_LOG_LEVEL=info
- NB_LISTEN_ADDRESS=:$NETBIRD_RELAY_PORT
- NB_EXPOSED_ADDRESS=$NETBIRD_RELAY_DOMAIN:$NETBIRD_RELAY_PORT
# todo: change to a secure secret
- NB_AUTH_SECRET=$NETBIRD_RELAY_AUTH_SECRET
ports:
- $NETBIRD_RELAY_PORT:$NETBIRD_RELAY_PORT
logging:
driver: "json-file"
options:
max-size: "500m"
max-file: "2"
`
1- docker compose down under the artifacts directory
2- Edit your docker-compose.yml.tmpl.traefik , then overwirte it with cp command as "docker-compose.yml." Then just run ./configure.sh
3- go to artifacts dir, docker compose up, then relay should be working.
Describe the problem
netbird status gives: reason: relay client not connected
I'm using my own selfhosted netbird server.
To Reproduce
Steps to reproduce the behavior:
2025-01-03T00:27:45+03:00 ERRO relay/client/dialer/ws/ws.go:36: failed to dial to Relay server 'ws://netbird.domain.com:33080': failed to WebSocket dial: failed to send handshake request: Get "http://netbird.domain.com:33080/relay": d.Dialer.DialContext: dial tcp 92.113.26.143:33080: connect: connection timed out
2025-01-03T00:27:50+03:00 ERRO client/internal/connect.go:249: failed to connect to any relay server: context deadline exceeded
2025-01-03T00:27:50+03:00 INFO relay/client/guard.go:68: try to pick up a new Relay server
2025-01-03T00:27:50+03:00 INFO relay/client/picker.go:72: try to connecting to relay server: rel://netbird.domain.com:33080
2025-01-03T00:27:50+03:00 INFO [relay: rel://netbird.domain.com:33080] relay/client/client.go:165: create new relay connection: local peerID: MfThRZtJfCAzzPvrLMfkjGkY1MNRCq15kejfET54RHw=, local peer hashedID: sha-9J7vtUU2mg/gV75vQ+mS1daMJJz0qj+6xnwGL5GhHbk=
Expected behavior
I hope relays' result should be 3/3 connected when I typed "netbird status -d"
Are you using NetBird Cloud?
Netbird Selfhosted
NetBird version
0.35.1
NetBird status -dA output:
Peers detail:
OS: linux/amd64
Daemon version: 0.35.1
CLI version: 0.35.1
Management: Connected to https://netbird.anon-paBa5.domain:443
Signal: Connected to https://netbird.anon-paBa5.domain:80
Relays:
[stun:netbird.anon-paBa5.domain:3478] is Available
[turn:netbird.anon-paBa5.domain:3478?transport=udp] is Available
[rel://netbird.anon-paBa5.domain:33080] is Unavailable, reason: relay client not connected
Nameservers:
FQDN: orion.netbird.selfhosted
NetBird IP: 100.72.198.15/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Networks: -
Peers count: 0/0 Connected
Do you face any (non-mobile) client issues?
.....
Screenshots
....
Additional context
....
The text was updated successfully, but these errors were encountered: