Skip to main content

Configuring firewalls

Learn how to configure firewalls for LiveKit Cloud.

On this page

Corporate firewalls

LiveKit uses WebSocket and WebRTC to transmit data and media. All transmissions are encrypted with TLS  and DTLS .

LiveKit Cloud requires access to a few domains in order to establish a connection. If you are behind a corporate firewall, please ensure outbound traffic is allowed to the following addresses and ports:

HostPortPurpose
*.livekit.cloudTCP: 443Signal connection over secure WebSocket
*.turn.livekit.cloudTCP: 443TURN /TLS. Used when UDP connection isn't viable
*.host.livekit.cloudUDP: 3478TURN/UDP servers that assist in establishing connectivity
all hosts (recommended)UDP: 50000-60000UDP connection for WebRTC
all hosts (recommended)TCP: 7881TCP connection for WebRTC
integrations.livekit.ioTCP: 443Frontend Krisp noise filter models, if used

In order to obtain the best audio and video quality, LiveKit recommends allowing access to the UDP ports listed above. Additionally, please ensure UDP hole-punching is enabled (or disable symmetric NAT). This helps machines behind the firewall to establish a direct connection to a LiveKit Cloud media server.

Minimum requirements

If wildcard hostnames are not allowed by your firewall or security policy, the following are the minimum set of hostnames required to connect to LiveKit Cloud:

HostPort
<your-subdomain>.livekit.cloudTCP 443
<your-subdomain>.turn.livekit.cloudTCP 443
<your-subdomain>.osaopaulo1a.production.livekit.cloudTCP 443
<your-subdomain>.osaopaulo1b.production.livekit.cloudTCP 443
<your-subdomain>.oashburn1a.production.livekit.cloudTCP 443
<your-subdomain>.oashburn1b.production.livekit.cloudTCP 443
<your-subdomain>.omarseille1a.production.livekit.cloudTCP 443
<your-subdomain>.omarseille1b.production.livekit.cloudTCP 443
<your-subdomain>.otokyo1a.production.livekit.cloudTCP 443
<your-subdomain>.otokyo1b.production.livekit.cloudTCP 443
<your-subdomain>.ophoenix1a.production.livekit.cloudTCP 443
<your-subdomain>.ophoenix1b.production.livekit.cloudTCP 443
<your-subdomain>.olondon1a.production.livekit.cloudTCP 443
<your-subdomain>.olondon1b.production.livekit.cloudTCP 443
<your-subdomain>.ochicago1a.production.livekit.cloudTCP 443
<your-subdomain>.ochicago1b.production.livekit.cloudTCP 443
<your-subdomain>.osingapore1a.production.livekit.cloudTCP 443
<your-subdomain>.osingapore1b.production.livekit.cloudTCP 443
<your-subdomain>.odubai1a.production.livekit.cloudTCP 443
<your-subdomain>.odubai1b.production.livekit.cloudTCP 443
<your-subdomain>.ohyderabad1a.production.livekit.cloudTCP 443
<your-subdomain>.ohyderabad1b.production.livekit.cloudTCP 443
<your-subdomain>.ojohannesburg1a.production.livekit.cloudTCP 443
<your-subdomain>.ojohannesburg1b.production.livekit.cloudTCP 443
<your-subdomain>.omumbai1a.production.livekit.cloudTCP 443
<your-subdomain>.omumbai1b.production.livekit.cloudTCP 443
<your-subdomain>.ofrankfurt1a.production.livekit.cloudTCP 443
<your-subdomain>.ofrankfurt1b.production.livekit.cloudTCP 443
<your-subdomain>.ojerusalem1a.production.livekit.cloudTCP 443
<your-subdomain>.ojerusalem1b.production.livekit.cloudTCP 443
<your-subdomain>.osydney1a.production.livekit.cloudTCP 443
<your-subdomain>.osydney1b.production.livekit.cloudTCP 443
<your-subdomain>.ozurich1a.production.livekit.cloudTCP 443
<your-subdomain>.ozurich1b.production.livekit.cloudTCP 443
<your-subdomain>.osanjose1a.production.livekit.cloudTCP 443
<your-subdomain>.osanjose1b.production.livekit.cloudTCP 443
<your-subdomain>.ojeddah1a.production.livekit.cloudTCP 443
<your-subdomain>.ojeddah1b.production.livekit.cloudTCP 443
<your-subdomain>.oosaka1a.production.livekit.cloudTCP 443
<your-subdomain>.oosaka1b.production.livekit.cloudTCP 443
<your-subdomain>.omontreal1a.production.livekit.cloudTCP 443
<your-subdomain>.omontreal1b.production.livekit.cloudTCP 443
<your-subdomain>.otoronto1a.production.livekit.cloudTCP 443
<your-subdomain>.otoronto1b.production.livekit.cloudTCP 443
<your-subdomain>.oqueretaro1a.production.livekit.cloudTCP 443
<your-subdomain>.oqueretaro1b.production.livekit.cloudTCP 443
Note

This list of domains is subject to change. Last updated 2026-07-21.

Static IPs

Static IP ranges are available for the Canada, EU, India, Japan, and US regions, and apply to realtime, SIP signaling and media, and webhook traffic. For the ranges, the services they cover, regional endpoints, and answers to common questions, see Static IPs in the Regions, regional endpoints, and static IPs topic.

Deep packet inspection

Proxies and firewalls that decrypt and inspect traffic, such as Zscaler, often break LiveKit connections, including TURN.

Exempt livekit.cloud and all of its subdomains from inspection. Regional signaling and TURN hosts are several levels deep, so make sure that your rule matches subdomains at any depth.

Troubleshooting connectivity

Run the LiveKit connection test  from the affected network and again from a network without the firewall, then compare the results to see which connection types the firewall blocks.

Connection timeouts

If your network policy doesn't allow UDP, allow TCP traffic on port 443 to *.turn.livekit.cloud, as explained in Corporate firewalls. If you still experience connection timeouts, you can force your clients to use TURN by setting the ICE transport policy to relay. This adds latency, so use it only for participants on restrictive networks or to confirm that the firewall is the cause.

const room = new Room();
await room.connect(url, token, {
rtcConfig: { iceTransportPolicy: 'relay' },
// Don't set iceServers, as this replaces LiveKit Cloud's TURN servers.
});
let room = Room()
try await room.connect(
url: url,
token: token,
// Don't set iceServers, as this replaces LiveKit Cloud's TURN servers.
connectOptions: ConnectOptions(iceTransportPolicy: .relay)
)
import io.livekit.android.ConnectOptions
import io.livekit.android.LiveKit
import livekit.org.webrtc.PeerConnection
val room = LiveKit.create(context)
room.connect(
url,
token,
ConnectOptions(
// Pass an empty list. Any ICE servers you set here or in ConnectOptions.iceServers
// replace LiveKit Cloud's TURN servers.
rtcConfig = PeerConnection.RTCConfiguration(emptyList()).apply {
iceTransportsType = PeerConnection.IceTransportsType.RELAY
},
),
)
final room = Room();
await room.connect(
url,
token,
connectOptions: const ConnectOptions(
// Don't set iceServers, as this replaces LiveKit Cloud's TURN servers.
rtcConfiguration: RTCConfiguration(
iceTransportPolicy: RTCIceTransportPolicy.relay,
),
),
);
<LiveKitRoom
serverUrl={url}
token={token}
connect={true}
connectOptions={{
rtcConfig: { iceTransportPolicy: 'relay' },
// Don't set iceServers, as this replaces LiveKit Cloud's TURN servers.
}}
>
</LiveKitRoom>
Ensure consistent UDP access

Forcing a relay doesn't force TCP. A relay connection can still use TURN over UDP, so if your network passes some UDP traffic but drops the rest, forcing a relay might not fix connection timeouts. In this situation, make UDP behavior consistent, preferably by allowing the UDP ports listed in the Corporate firewalls table, or else by blocking them.