SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-10 01:12:51 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

question about multiple coturn servers in selfhosted #501

New Issue
Open
opened 2025-11-20 05:12:36 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:12:36 -05:00
Owner
Copy Link

Originally created by @Fantu on GitHub (Nov 3, 2023).

Hi, now is possible set multiple coturn server, FWIK for example:

    "TURNConfig": {
        "TimeBasedCredentials": false,
        "CredentialsTTL": "12h0m0s",
        "Secret": "secret",
        "Turns": [
            {
                "Proto": "udp",
                "URI": "turn:server1.example:3478",
                "Username": "self",
                "Password": "password"
            },
            {
                "Proto": "udp",
                "URI": "turn:server2.example:3478",
                "Username": "self",
                "Password": "password"
            }
        ]
    },

How are these used?
Is each request sent to a random coturn server on the list or does it follow the order and use the subsequent ones if the first one is not reachable?

Originally created by @Fantu on GitHub (Nov 3, 2023). Hi, now is possible set multiple coturn server, FWIK for example: ``` "TURNConfig": { "TimeBasedCredentials": false, "CredentialsTTL": "12h0m0s", "Secret": "secret", "Turns": [ { "Proto": "udp", "URI": "turn:server1.example:3478", "Username": "self", "Password": "password" }, { "Proto": "udp", "URI": "turn:server2.example:3478", "Username": "self", "Password": "password" } ] }, ``` How are these used? Is each request sent to a random coturn server on the list or does it follow the order and use the subsequent ones if the first one is not reachable?
saavagebueno added the documentationmissing-docs labels 2025-11-20 05:12:36 -05:00
saavagebueno commented 2025-11-20 05:12:37 -05:00
Author
Owner
Copy Link

@bcmmbaga commented on GitHub (Nov 3, 2023):

Hi @Fantu, They are all used at the same time. It always connects to all the URLs there and checks them for connectivity. If one is able to connect, it will use it.

@bcmmbaga commented on GitHub (Nov 3, 2023): Hi @Fantu, They are all used at the same time. It always connects to all the URLs there and checks them for connectivity. If one is able to connect, it will use it.
saavagebueno commented 2025-11-20 05:12:37 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Nov 3, 2023):

the agent will connect to all TURN servers, and them it will use these connections to check if it can communicate with the other peers. If one responds faster, it will use it instead of the other, but there is no way to order these checks besides how you configure them.

Once a turn is selected and used for the connection, the agents periodically send checks to validate if they are still available; if something goes wrong with the checks, the negotiation is restarted. There is no use of the next relay server in this case (not yet)

In that sense, ICE chooses the faster one to reply to the initial check. Which, in many cases, is the one with a lower latency

@mlsmaycon commented on GitHub (Nov 3, 2023): the agent will connect to all TURN servers, and them it will use these connections to check if it can communicate with the other peers. If one responds faster, it will use it instead of the other, but there is no way to order these checks besides how you configure them. Once a turn is selected and used for the connection, the agents periodically send checks to validate if they are still available; if something goes wrong with the checks, the negotiation is restarted. There is no use of the next relay server in this case (not yet) In that sense, ICE chooses the faster one to reply to the initial check. Which, in many cases, is the one with a lower latency
saavagebueno commented 2025-11-20 05:12:38 -05:00
Author
Owner
Copy Link

@Fantu commented on GitHub (Nov 3, 2023):

thanks to all for the replies
the @mlsmaycon one is the more complete, I suggest should be used to improve the documentation as can be useful to know

@Fantu commented on GitHub (Nov 3, 2023): thanks to all for the replies the @mlsmaycon one is the more complete, I suggest should be used to improve the documentation as can be useful to know
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 documentation missing-docs
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#501
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?