TURN is dead?

[1nerdyguy]

Just seeing [management] Delete TURNConfig section from script by @braginini in #4639

Does this mean TURN is no longer required at all, and can be removed from existing deployments?

Long live relay?

[rtgiskard]

Long live relay?

I guess Yes

[1350962574]

You need to start a new relay container according to the latest deployment script and configure the wss reverse proxy and add the relay parameter to management.json

[1350962574]

Because Stun still requires support from Coturn images From my iPhone

…

------------------ Original ------------------ From: laweschan ***@***.***> Date: Wed,Oct 22,2025 11:14 AM To: netbirdio/netbird ***@***.***> Cc: handsome boy ***@***.***>, Comment ***@***.***> Subject: Re: [netbirdio/netbird] TURN is dead? (Issue #4678) laweschan left a comment (netbirdio/netbird#4678) but why the script still require coturn image download and deployment even the contrun part has remove from [management] section ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[laweschan]

got it, thanks for help @1350962574

[PowershellScripter]

Is there updated documentation for this? I have both the relay and coturn containers. The wss relay works but the coturn for me never has. Do I just remove the coturn container from my environment?

Netbird has yet to update their documentation on the process of a complete move over to the wss relay and removing cortunr from the env

[1350962574]

I will organize a copy later. markdown document for you From my iPhone

…

------------------ Original ------------------ From: PowershellScripter ***@***.***> Date: Thu,Oct 23,2025 7:20 AM To: netbirdio/netbird ***@***.***> Cc: handsome boy ***@***.***>, Mention ***@***.***> Subject: Re: [netbirdio/netbird] TURN is dead? (Issue #4678) PowershellScripter left a comment (netbirdio/netbird#4678) Is there updated documentation for this? I have both the relay and coturn containers. The wss relay works but the coturn for me never has. Do I just remove the coturn container from my environment? Netbird has yet to update their documentation on the process of a complete move over to the wss relay and removing cortunr from the env — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[1350962574]

@PowershellScripter

Configure Netbird with Relay Service

This document outlines the steps to add a Netbird relay container, update configuration files, and set up reverse proxy for the relay service.

1. Update docker-compose.yml to Add Relay Container

Edit your docker-compose.yml file and include the following configuration for the relay service:

yaml

relay:
  image: netbirdio/relay:latest
  restart: unless-stopped
  networks: [netbird]
  environment:
    - NB_LOG_LEVEL=info
    - NB_LISTEN_ADDRESS=:80
    - NB_EXPOSED_ADDRESS=rels://<domains.com>:443
    - NB_AUTH_SECRET=<your-secret>
  logging:
    driver: "json-file"
    options:
      max-size: "500m"
      max-file: "2"

2. Modify management.json to Add Relay Configuration and Remove TURN

Edit the management.json file to include the relay parameters and remove the TURN configuration:

Add Relay Configuration:

json

"Relay": {
  "Addresses": ["rels://<domains.com>:443"],
  "CredentialsTTL": "24h0m0s",
  "Secret": "<your-secret>"
},

Remove TURN Configuration:

Delete the following section:

json

"TURNConfig": {
  "Turns": [
      {
          "Proto": "udp",
          "URI": "turn:$NETBIRD_DOMAIN:$TURN_LISTENING_PORT",
          "Username": "$TURN_USER",
          "Password": "$TURN_PASSWORD"
      }
  ],

3. Update Caddyfile to Add WSS Reverse Proxy for Relay

Edit your Caddyfile and include the reverse proxy configuration for the relay service:

caddyfile

reverse_proxy /relay* relay:80

Important Note

Do NOT remove the Coturn image. Coturn is still required to provide STUN services, which are necessary for P2P connectivity. We are only switching the TURN functionality to netbirdio/relay while retaining Coturn for STUN support.

[PowershellScripter]

@1350962574 Thank you for this information. I already had the wss relay in place with the json section, so all I had to do was remove the TURN section. This actually dropped my [netbird status -d] from 14 seconds to 6 seconds, but my STUN still isnt working and I cant seem to figure out why. But, thats a different situation altogether. I appreciate the quick follow up and other than the other issue im facing, im all updated and TURN has been configured for STUN only, so thank you.

[1350962574]

@PowershellScripter
The operation method is based on the latest fast hosting script analysis, and will not cause stun to not work properly, but I have not found such a problem. The problem may lie somewhere else. You need to check it.

[PowershellScripter]

@1350962574 No I know this wouldnt cause STUN to not work. STUN hasnt worked for me since I setup my netbird deployment and Ive been debugging to try to get it work. Another user reported that my delay in the requested status information most likely has to do with a timeout when trying to reach the sever and not getting a proper response.
The wss relay is working properly though, so thank you.

[1350962574]

you can referWatching the mountains, Tang Sibo can climLet's see if he can work properly 

…

------------------ Original ------------------ From: PowershellScripter ***@***.***> Date: Thu,Oct 23,2025 11:20 AM To: netbirdio/netbird ***@***.***> Cc: handsome boy ***@***.***>, Mention ***@***.***> Subject: Re: [netbirdio/netbird] TURN is dead? (Issue #4678) PowershellScripter left a comment (netbirdio/netbird#4678) @1350962574 No I know this wouldnt cause STUN to not work. STUN hasnt worked for me since I setup my netbird deployment and Ive been debugging to try to get it work. Another user reported that my delay in the requested status information most likely has to do with a timeout when trying to reach the sever and not getting a proper response. The wss relay is working properly though, so thank you. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[PowershellScripter]

 You can referWatching the mountains, Tang Sibo can climLet's see if he can work properly
…

huh? 😅

[PowershellScripter]

you can referWatching the mountains, Tang Sibo can climLet's see if he can work properly

…

So I have the udp config set properly for it. I think its something with the cloud provider we use, but im still investigating

[1350962574]

replying using an email client, it may not Since I replied using an email client, the content may be incomplete https://github.com/user-attachments/assets/5fe04463-d558-4bec-8950-5aa4d1312cdc 发自我的iPhone

…

------------------ Original ------------------ From: PowershellScripter ***@***.***> Date: Thu,Oct 23,2025 11:27 AM To: netbirdio/netbird ***@***.***> Cc: handsome boy ***@***.***>, Mention ***@***.***> Subject: Re: [netbirdio/netbird] TURN is dead? (Issue #4678) PowershellScripter left a comment (netbirdio/netbird#4678)  You can referWatching the mountains, Tang Sibo can climLet's see if he can work properly … huh? 😅 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[PowershellScripter]

replying using an email client, it may not Since I replied using an email client, the content may be incomplete

…

I see that there is a tcp STUNS in that config. Am I suppsoed to had udp and tcp?