@nebulon @girish @d19dotca Thank's a lot @d19dotca ! For me is a little bit complex append that command in cronjob and I don't know if Cloudron make some integrity test at boot time to try to check if turn is on or off.

Another solution is to use VPS provided firewall to lock that doors... But as @nebulon wrote, one improvement could be add rate-limiting and/or start that services on demand.

Thank's all for your answer 🙂

Found the template with:

sudo grep -rnw '/' -e 'rtcsec'

@girish We're already done.. had to have udp ports open in the 50,000 range and TURN/STUN ports.

Thanks for thinking of me though 😛

@girish @nebulon Encountering the exact same issue with Matrix with the same network setup and same individual I was testing Nextcloud Talk with. Any ideas on how I can proceed here? I'm a bit lost but it looks to be either a TURN or network issue. The only thing I've changed lately is bridging my ISP modem to a new router I got. I have forwarded the ports I believe I need. (Also I sent new screenshots to the support email)

Not sure if this is related but in the logs for Surfer, which I have as a redirect for the root domain, I am getting a 404 for the matrix .well-known constantly.

GET /.well-known/matrix/client 404 1.083 ms - 328

Were you ever able to look into this @girish?

Thanks for your coturn write up. We did refer to that when we added turn support in Cloudron 5.1, in fact.

On how to update: you can just uninstall turn server (and also free up the turn ports on the host). The turn server is exposed at my.domain.com, so no need to setup an extra A record. The nextcloud talk app is pre-configured to use the integrated turn server. You can just "re-configure" the app (for example, just go to Location and click save without making any changes) and it should overwrite your old turn settings and put the new one.