# 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:** 1\ **Showing post:** 2
**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! --- _[View the full topic](https://help.nextcloud.com/t/cant-get-turn-server-to-work/49872)._