Voice does not work on my self-hosted server
If chat works but voice has no audio or drops, UDP port 7070 is usually blocked, so open it and open 7070 as TCP for the fallback.
Chat and voice use different ports, so chat can work while voice fails.
Causes and fixes
- UDP 7070 is blocked. This is the most common cause. Allow UDP
7070in the server's firewall and forward it on your router to the server's local IP. If you changedUDP_PORT, use that port. See Ports and port forwarding. - One member's network blocks UDP. Some ISPs, mobile carriers, schools and offices do this. The server has a TCP fallback on the same port number, on by default. Allow and forward
7070as TCP too, then confirm in Server Settings > General > Network Diagnostics that the TCP fallback port is reachable. It gets past networks that block UDP, but not strict firewalls that only allow port 443. - A member joins voice, then drops after a few seconds. They are probably behind carrier-grade NAT. Make your server reachable over IPv6 (see Host behind CGNAT or Starlink), or run your own TURN relay such as coturn and set
TURN_SERVER_URL,TURN_USERNAMEandTURN_PASSWORD. See Environment variables. - Docker uses bridge networking. Docker's NAT can break voice connections. On Linux, use host networking. On Docker Desktop, where host mode does not reach your real network, publish the ports and set
PUBLIC_IPif the detected address is wrong. See Run a self-hosted server with Docker. - The TCP fallback is turned off.
WEBRTC_TCP_PORTset to0disables it, and the log says so at startup. Remove the variable to turn it back on.