SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-03 04:32:27 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

relay client not connected #1538

New Issue
Closed
opened 2025-11-20 05:32:27 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:32:27 -05:00
Owner
Copy Link

Originally created by @Onur-Cansever on GitHub (Jan 2, 2025).

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:

  1. Start traefik
  2. Up netbird compose
  3. Try to connect netbird server from cli on desktop
  4. See error: [rel://netbird.domain.com:33080] is Unavailable, reason: relay client not connected
  5. When I tail the "/var/log/netbird/client.log" file: I see:
  6. 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

....

Originally created by @Onur-Cansever on GitHub (Jan 2, 2025). **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: 1. Start traefik 2. Up netbird compose 3. Try to connect netbird server from cli on desktop 4. See error: [rel://netbird.domain.com:33080] is Unavailable, reason: relay client not connected 5. When I tail the "/var/log/netbird/client.log" file: I see: 6. 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** ....
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:32:27 -05:00
saavagebueno commented 2025-11-20 05:32:28 -05:00
Author
Owner
Copy Link

@Onur-Cansever commented on GitHub (Jan 3, 2025):

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.

@Onur-Cansever commented on GitHub (Jan 3, 2025): 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.
saavagebueno commented 2025-11-20 05:32:29 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 28, 2025):

Hello @Onur-Cansever,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @Onur-Cansever, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:32:29 -05:00
Author
Owner
Copy Link

@Onur-Cansever commented on GitHub (May 1, 2025):

I checked the latest stable files, It seems fixed, thanks for your attention.

@Onur-Cansever commented on GitHub (May 1, 2025): I checked the latest stable files, It seems fixed, thanks for your attention.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label triage-needed waiting-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1538
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?