# Can't get TURN server to work **URL:** \ **Category:** 💬 Talk (spreed)\ **Created:** [March 19, 2019, 7:28pm UTC](https://help.nextcloud.com/t/cant-get-turn-server-to-work/49872 "2019-03-19T19:28:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![linuxdude314](https://help.nextcloud.com/letter_avatar/linuxdude314/32/5_5575768a8748004e209b776fc1b2916d.png) [@linuxdude314](https://help.nextcloud.com/u/linuxdude314)\ **Post date:** [March 19, 2019, 7:28pm UTC](https://help.nextcloud.com/t/cant-get-turn-server-to-work/49872/1 "2019-03-19T19:28:53Z")
Hello, I’ve installed the Nextcloud Talk app and am having some trouble making it work outside my local network. I understand in order to achieve the functionality I desire, I should install and configure my own TURN server. To this end, I have done so on a VPS following instructions provided by this community. My config is as follows: **_/etc/turnserver.conf_** ``` listening-port=3478 fingerprint use-auth-secret static-auth-secret= realm= total-quota=100 bps-capacity=0 stale-nonce no-loopback-peers no-multicast-peers log-file=/var/log/coturn.log ``` When users and guests try to join calls, some can hear my microphone, and some cannot. For others the screen is blank and they hear no audio. On the turn server I see logs like the following: ``` 2116: session 007000000000000019: realm user <>: incoming packet BINDING processed, success 2126: session 007000000000000019: realm user <>: incoming packet BINDING processed, success 2127: session 007000000000000019: realm user <>: incoming packet BINDING processed, success 2137: session 007000000000000019: realm user <>: incoming packet BINDING processed, success 2146: session 007000000000000019: closed (2nd stage), user <> realm origin <>, local 172.245.22.151:3478, remote 96.38.143.134:48364, reason: allocation watchdog determined stale session state 2147: handle_udp_packet: New UDP endpoint: local addr 172.245.22.151:3478, remote addr 96.38.143.134:48364 2147: session 007000000000000020: realm user <>: incoming packet BINDING processed, success 2157: session 007000000000000020: realm user <>: incoming packet BINDING processed, success ``` Note: I’ve redacted the realm URL in the logs, which is set to the FQDN of the Nextcloud instance. When I test the configuration in Settings -\> Talk, I get a little exclamation arrow, not a green check mark. At this point I’m somewhat stumped; am I missing something glaring? Please help! Thanks, -Linuxdude ---
**Author:** ![linuxdude314](https://help.nextcloud.com/letter_avatar/linuxdude314/32/5_5575768a8748004e209b776fc1b2916d.png) [@linuxdude314](https://help.nextcloud.com/u/linuxdude314)\ **Post date:** [March 20, 2019, 6:33am UTC](https://help.nextcloud.com/t/cant-get-turn-server-to-work/49872/2 "2019-03-20T06:33:17Z")
I somewhat miraculously figured this out… After almost giving up, I decided to look at the script provided in github: > This config provided by the script contained one line different than any recommendations I’ve seen on this forum: lt-cred-mech This guide specifically mentions it can’t be enabled when use-auth-secret is also enabled, but in my case, it only works with both config options set. > [@HowTo: Setup Nextcloud Talk with TURN server](https://help.nextcloud.com/t/howto-setup-nextcloud-talk-with-turn-server/30794): > > Background The configuration of Nextcloud Talk mainly depends on your desired usage: As long as it shall be used only within one local network, nothing should be needed at all. Just verify that all browsers support the underlying [WebRTC](https://en.wikipedia.org/wiki/WebRTC) protocol (all famous ones do on current versions) and you should be good to go. Talk tries to establish a direct [peer-to-peer (P2P)](https://en.wikipedia.org/wiki/Peer-to-peer) connection, thus on connections throughout the local network (behind a [NAT](https://en.wikipedia.org/wiki/Network_address_translation)/router), clients do not only need to know each others … Cheers! ---
**Author:** ![MichaIng](https://help.nextcloud.com/user_avatar/help.nextcloud.com/michaing/32/2125_2.png) [@MichaIng](https://help.nextcloud.com/u/MichaIng)\ **Post date:** [March 20, 2019, 3:10pm UTC](https://help.nextcloud.com/t/cant-get-turn-server-to-work/49872/3 "2019-03-20T15:10:41Z")
Jep thanks for the hint. I removed it since it throws warnings as can be seen from my changelog in OT. But obviously this is only the case for newer coTURN versions while in older one it’s still required. I will re-add it with the hint. Which version of coTURN do you use? I will also try to check the commits to know from which version on this setting should be removed and until which version it needs to stay. ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [December 4, 2024, 9:34am UTC](https://help.nextcloud.com/t/cant-get-turn-server-to-work/49872/4 "2024-12-04T09:34:47Z")
---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [December 11, 2024, 2:40pm UTC](https://help.nextcloud.com/t/cant-get-turn-server-to-work/49872/5 "2024-12-11T14:40:03Z")