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

Unable to connect to turn server. Stun server works #923

New Issue
Closed
opened 2025-11-20 05:19:58 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:19:58 -05:00
Owner
Copy Link

Originally created by @alex-ritter on GitHub (May 24, 2024).

Describe the problem

When connecting to Netbird externally, I'm unable to ping any peers. When connected locally everything works fine. Running netbird status -d it seems like I'm connected to the stun relay just fine but the turn relay is causing an issue.

[stun:netbird..com:3478] is Available
[turn:netbird..com:3478?transport=udp] is Unavailable, reason: allocate: Allocate error response (error 401: Unauthorized)

Management logs, dashboard logs, api logs all look fine. The only backend error I'm seeing is in the Coturn service. When running docker compose Coturn logs I get the following errors

coturn-1 | 133802: (12): ERROR: check_stun_auth: user self credentials are incorrect

To Reproduce

This is most likely a configuration / networking issue. To reproduce this on my side

  1. Install a new peer agent using the latest netbird agent or in my case 0.27.7
  2. Connect to netbird successfully
  3. Try to ping another peer either by the netbird IP 100.xx.xx.xx or by their host name xxxxx.netbird.example

Expected behavior

Be able to ping the host name xxxx.netbird.example. All routes are setup by default, this is a default instance of netbird so all routes should be enabled.

Are you using NetBird Cloud?

No, this is self hosted

NetBird version

0.27.7

NetBird status -d output:

OS: windows/amd64
Daemon version: 0.27.7
CLI version: 0.27.7
Management: Connected to https://netbird..com:443
Signal: Connected to https://netbird..com:443
Relays:
[stun:netbird..com:3478] is Available
[turn:netbird..com:3478?transport=udp] is Unavailable, reason: allocate: Allocate error response (error 401: Unauthorized)
Nameservers:
FQDN: netbird.*
NetBird IP: 100.../
Interface type: Userspace
Quantum resistance: false
Routes: -
Peers count: 0/3 Connected

Additional context

Most likely this is a configuration / networking issue. This is how my netbird is hosted.
Domain -> Cloudflare (non-proxied) -> Reverse Proxy (nginx) -> Netbird.

I use unifi and unifi firewall. For now I'm trying to set everything to allow all just to get this to work. This is my current firewall config.

I have a vlan for monitoring, a vlan for external services, and a vlan for my personal devices.
monitoring vlan has access to all other vlans
external vlan has access to all other vlans

nginx reverse proxy is on the external vlan, has port 80, 443 exposed.
netbird is on the monitoring vlan, has port 3478, 49152 - 65535, 33073, and 10000 exposed.

Only reason why I think this is a networking issue is because I can connect to peers locally, but externally I can't. But that just might be the difference between the 'stun' and the 'turn' relay since a lot of this is new to me. I'd like opinions as I'm looking at this later today. I'll post any fixes if I find any.

Originally created by @alex-ritter on GitHub (May 24, 2024). **Describe the problem** When connecting to Netbird externally, I'm unable to ping any peers. When connected locally everything works fine. Running netbird status -d it seems like I'm connected to the stun relay just fine but the turn relay is causing an issue. [stun:netbird.***.com:3478] is Available [turn:netbird.***.com:3478?transport=udp] is Unavailable, reason: allocate: Allocate error response (error 401: Unauthorized) Management logs, dashboard logs, api logs all look fine. The only backend error I'm seeing is in the Coturn service. When running docker compose Coturn logs I get the following errors coturn-1 | 133802: (12): ERROR: check_stun_auth: user self credentials are incorrect **To Reproduce** This is most likely a configuration / networking issue. To reproduce this on my side 1. Install a new peer agent using the latest netbird agent or in my case 0.27.7 2. Connect to netbird successfully 3. Try to ping another peer either by the netbird IP 100.xx.xx.xx or by their host name xxxxx.netbird.example **Expected behavior** Be able to ping the host name xxxx.netbird.example. All routes are setup by default, this is a default instance of netbird so all routes should be enabled. **Are you using NetBird Cloud?** No, this is self hosted **NetBird version** 0.27.7 **NetBird status -d output:** OS: windows/amd64 Daemon version: 0.27.7 CLI version: 0.27.7 Management: Connected to https://netbird.****.com:443 Signal: Connected to https://netbird.****.com:443 Relays: [stun:netbird.****.com:3478] is Available [turn:netbird.****.com:3478?transport=udp] is Unavailable, reason: allocate: Allocate error response (error 401: Unauthorized) Nameservers: FQDN: ****netbird.***** NetBird IP: 100.**.**.**/** Interface type: Userspace Quantum resistance: false Routes: - Peers count: 0/3 Connected **Additional context** Most likely this is a configuration / networking issue. This is how my netbird is hosted. Domain -> Cloudflare (non-proxied) -> Reverse Proxy (nginx) -> Netbird. I use unifi and unifi firewall. For now I'm trying to set everything to allow all just to get this to work. This is my current firewall config. I have a vlan for monitoring, a vlan for external services, and a vlan for my personal devices. monitoring vlan has access to all other vlans external vlan has access to all other vlans nginx reverse proxy is on the external vlan, has port 80, 443 exposed. netbird is on the monitoring vlan, has port 3478, 49152 - 65535, 33073, and 10000 exposed. Only reason why I think this is a networking issue is because I can connect to peers locally, but externally I can't. But that just might be the difference between the 'stun' and the 'turn' relay since a lot of this is new to me. I'd like opinions as I'm looking at this later today. I'll post any fixes if I find any.
saavagebueno added the triage-needed label 2025-11-20 05:19:58 -05:00
saavagebueno commented 2025-11-20 05:19:58 -05:00
Author
Owner
Copy Link

@alex-ritter commented on GitHub (May 24, 2024):

Created a slack message for debugging purposes and just general questions I have. For documentation purposes I'll add the link to the message here.

https://netbirdio.slack.com/archives/C05T5K65X7U/p1716567332360629

@alex-ritter commented on GitHub (May 24, 2024): Created a slack message for debugging purposes and just general questions I have. For documentation purposes I'll add the link to the message here. https://netbirdio.slack.com/archives/C05T5K65X7U/p1716567332360629
saavagebueno commented 2025-11-20 05:19:59 -05:00
Author
Owner
Copy Link

@alex-ritter commented on GitHub (May 24, 2024):

This problem kind of just fixed itself...

I enabled verbose logging and tried to run the process again and it worked fine. Netbird worked completely end to end

@alex-ritter commented on GitHub (May 24, 2024): This problem kind of just fixed itself... I enabled verbose logging and tried to run the process again and it worked fine. Netbird worked completely end to end
saavagebueno commented 2025-11-20 05:19:59 -05:00
Author
Owner
Copy Link

@firekirin67 commented on GitHub (Sep 3, 2024):

This problem kind of just fixed itself...

I enabled verbose logging and tried to run the process again and it worked fine. Netbird worked completely end to end

Could you please tell me how you resolved it? It seems I've encountered the same issue as you.

@firekirin67 commented on GitHub (Sep 3, 2024): > This problem kind of just fixed itself... > > I enabled verbose logging and tried to run the process again and it worked fine. Netbird worked completely end to end Could you please tell me how you resolved it? It seems I've encountered the same issue as you.
saavagebueno commented 2025-11-20 05:19:59 -05:00
Author
Owner
Copy Link

@alex-ritter commented on GitHub (Sep 4, 2024):

This problem kind of just fixed itself...
I enabled verbose logging and tried to run the process again and it worked fine. Netbird worked completely end to end

Could you please tell me how you resolved it? It seems I've encountered the same issue as you.

I have a hint of what it was, I had the same issue after getting it working externally. Seems like restarting my computer or refreshing DNS cache worked. Also sometimes I need to restart netbird but that gives a different error.

Haven't had any issues for a while, make sure ports are forward, settings are correct, etc.

Also "sometimes I need to restart netbird but that gives a different error." this may be because of my deployment process before, I deploy netbird using Infrastructure as Code so this may not be a netbird issue.

@alex-ritter commented on GitHub (Sep 4, 2024): > > This problem kind of just fixed itself... > > I enabled verbose logging and tried to run the process again and it worked fine. Netbird worked completely end to end > > Could you please tell me how you resolved it? It seems I've encountered the same issue as you. I have a hint of what it was, I had the same issue after getting it working externally. Seems like restarting my computer or refreshing DNS cache worked. Also sometimes I need to restart netbird but that gives a different error. Haven't had any issues for a while, make sure ports are forward, settings are correct, etc. Also "sometimes I need to restart netbird but that gives a different error." this may be because of my deployment process before, I deploy netbird using Infrastructure as Code so this may not be a netbird issue.
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
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#923
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?