May i know livekit's turnServerUri?
# ask-ai
b
May i know livekit's turnServerUri?
✅ 1
t
Thanks for reaching out, G. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I can help with that. Are you using a self‑hosted LiveKit server or LiveKit Cloud? The correct
turnServerUri
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 elements
b
Its cloud based
t
Thanks — that helps. For LiveKit Cloud the TURN servers are provided for you and reachable via the turn.livekit.cloud domain. A few practical details: • TURN hostname pattern: *.turn.livekit.cloud • Recommended port/protocol: TCP on port 443 (this is firewall-friendly and mimics HTTPS traffic) • When UDP is allowed, TURN will also work over UDP, but TCP/443 is the reliable option for restricted networks. If you need to whitelist traffic or allow through corporate proxies/firewalls: • Whitelist
*.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