# Getting turn server to work

**URL:** <https://help.nextcloud.com/t/getting-turn-server-to-work/121733>\
**Category:** 💬 Talk (spreed)\
**Tags:** nc21\
**Created:** [August 11, 2021, 5:53pm UTC](https://help.nextcloud.com/t/getting-turn-server-to-work/121733 "2021-08-11T17:53:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mactrent](https://help.nextcloud.com/letter_avatar/mactrent/32/6_22734026db12803ebb3e059622ac3534.png) [@mactrent](https://help.nextcloud.com/u/mactrent)\
**Post date:** [August 11, 2021, 6:27pm UTC](https://help.nextcloud.com/t/getting-turn-server-to-work/121733/2 "2021-08-11T18:27:29Z")

</div>

That error would typically mean that another service is already listening on the port you want (443). Do you have a web server or another service listening on this port? Is there maybe another coturn process already running?  
You can use `ss -l4` to see what ports your services are listening to in the IPv4 space, and you can use `ps -A|grep coturn` to look specifically for other coturn processes.

Another possibility is that the user account that’s running coturn doesn’t have permission to run on low-numbered ports. Did you follow the instructions below “Anpassung des systemd für die Bindung von Coturn auf eine Port \< 1024.” in the article?

If your server is running behind NAT, it won’t be able to listen on the WAN IP. In that case, the config [section](https://github.com/coturn/coturn/blob/master/examples/etc/turnserver.conf#L108) for AWS (and other NAT) users might be helpful. There’s also [this how-to](https://help.nextcloud.com/t/howto-setup-nextcloud-talk-with-turn-server/30794) on the forums, which you can compare against your article to see what’s different.

---

_[View the full topic](https://help.nextcloud.com/t/getting-turn-server-to-work/121733)._