I've set up my homeserver via matrix-docker-ansible-deploy, but made the mistake of using my domain as ansible_host variable at first. I think that is why now my Coturn server doesn't work as intended. Calls can only be made (in Element) when I enable turn.matrix.org as an alternative in the settings.
Since the initital setup, I've correctly replaced the domain with the server IP in the ansible inventory file and reran just setup-all, but I still can't make calls via my homeserver.
- Is it likely that the mistake I made is causing this issue?
- What can I do to correct the Coturn configuration or otherwise fix this issue?
EDIT:
I've found this in the docs: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-turn.md#manually-defining-your-public-ip
I'll try this and report back.
EDIT2: This did not fix the issue.
The homeserver incl. Coturn is running on a VPS, no ports blocked.
The clients are in different networks. Everything should just work, but it doesn't for some reason.
@Lemmchen the different client-networks csn be the problem.
Some providers block webrtc or stun/turn...
Did you try to test your coturn on
webrtc.github.io/samples/src/c…
Delete all servers there and fill in your stun and turn (turn incl. credentials) andvtest ist.
You should get relay (=turn) and srflx (=stun) marked entries
The test correctly gathers the
srflxcandidates, so STUN should be working. But I can't get it to findrelaycandidates, so I guess TURN isn't?@Lemmchen
This is only stun.
For a working turn you need also "relay" entries