brave-author-62043
03/25/2026, 11:31 AMtall-airline-16756
03/25/2026, 11:32 AMtall-airline-16756
03/25/2026, 11:32 AMturnServerUri depends on how LiveKit is deployed:
• If you’re using LiveKit Cloud, the TURN URI is provided per-room/tenant from the cloud service (it’s not a single hardcoded public URI).
• If you’re self‑hosting, the TURN URI is whatever you configured for your TURN server (for example, a Coturn instance) and is set in your LiveKit server config.
Could you tell me which deployment you’re on (self‑hosted or Cloud)? If self‑hosted, please share how you deployed your TURN server (Coturn, other) and any relevant config or desired domain, and I’ll tell you exactly how to construct the turnServerUri and where to set it in LiveKit.
, with interactive elementsbrave-author-62043
03/25/2026, 11:33 AMtall-airline-16756
03/25/2026, 11:33 AM*.turn.livekit.cloud on TCP/443.
• If you use Zscaler with Deep Packet Inspection, create a bypass rule like: url.domain=turn.livekit.cloud detect_protocol(no) so TURN traffic is not blocked.
If you want, tell me:
• The specific client environment (browser/mobile/embedded) or network rules you’re facing, and I’ll suggest the exact client-side or firewall settings to ensure connectivity. Sources: Firewall Tips | Zscaler proxy configuration, with interactive elements