I don’t get this. nextcloud’s STUN obviously doesn’t run your ..ts.net domain? be aware STUN and TURN are often mentioned together but both are completely different techniques
- STUN only tells you about external IP which your connection exposes (if you are lucky your firewall allow inbound connections for each open outbound connection)
- TURN actively participates in connection and relays traffic from one endpoint to another - it is required if both client can’t talk directly to each other e.g. if both are behind NAT - this is a reason why TURN requires many bandwidth and cpu power so almost no free services exist
my coturn is running a separate container
coturn:
image: coturn/coturn
container_name: coturn
restart: unless-stopped
ports:
- 3478:3478
- 3478:3478/udp
- 50000-50099:50000-50099/udp
- 9641:9641
environment:
- DETECT_EXTERNAL_IP=yes
- DETECT_RELAY_IP=yes
command:
- -n
- --log-file=/var/turn.log
- --realm=${COTURN_FQDN}
- --use-auth-secret
- --static-auth-secret=${COTURN_SECRET}
- --verbose
volumes:
- ./coturn/:/var/
- ./turnserver.conf:/etc/coturn/turnserver.conf
networks:
- proxy
I don’t have the conf right now but nothing special there I think.
Port forward from public IP/interface to :3478 tcp and udp (but udp is most important). 50000k range is optional but if you can afford to open is it allows more different media path and potentially faster connects.
Look through existing topics
- Coturn on VPS with NGINX Proxy Manager Connecting to VM in a VLAN (All This Trouble for Nextcloud Talk)
- High Performance Backend for Talk on Nextcloud with Docker - and especially backlinks to it
likely you find similar issues with solutions.