Configure network and firewall requirements for Kaltura Edge Server

Last Modified on 08/30/2026 6:34 pm IDT

About

Kaltura Edge Server (KES) requires access to specific network ports and Kaltura domains to communicate with users on your internal network and with the Kaltura cloud.

Use the requirements below to configure your organization's network and firewall rules.

If your organization uses Chrome 142 or later, browser-level Local Network Access (LNA) restrictions can also affect communication with KES. These requirements are separate from your firewall configuration.

Network port requirements

Configure the following network ports based on the source and destination.

Port	Source	Destination
`443`	Internal user	Kaltura Edge Server
`80`	Internal user	Kaltura Edge Server
`443`	Kaltura Edge Server	Kaltura cloud
`80`	Kaltura Edge Server	Kaltura cloud
`22`	Administrator	Kaltura Edge Server

Allow Kaltura domains over port 443

Allow KES to connect to:

https://*.kaltura.com

If your firewall doesn't support wildcard domains, allow the following domains individually:

cfvod.kaltura.com
cdnapi.kaltura.com
klive.kaltura.com
www.kaltura.com
fstlive.kaltura.com
cdnapisec.kaltura.com
ecdnmonitor.kaltura.com

Depending on your environment, also allow:

https://kalsegsec-a.akamaihd.net - Alternative CDN domain
https://klive-a.akamaihd.net - Legacy Live CDN
https://kalseglive-a.akamaihd.net - Alternative Live CDN
https://*.kaltura.io - RPM repository and file exchange
http://*.kaltura.org

Allow Kaltura domains over port 80

Allow KES to connect to:

http://*.kaltura.com

If your firewall doesn't support wildcard domains, allow the following domains individually:

cfvod.kaltura.com
cdnapi.kaltura.com
klive.kaltura.com
www.kaltura.com
fstlive.kaltura.com
cdnapisec.kaltura.com
ecdnmonitor.kaltura.com

Configure browser Local Network Access

Firewall access alone might not be sufficient for users accessing KES from browsers that enforce Local Network Access (LNA) restrictions.

Starting with Chrome 142, requests from public websites to private or local network addresses can be restricted by the browser. This can affect Kaltura eCDN environments where a public-facing Kaltura domain communicates with KES or peers on your internal network.

No changes are required in Kaltura products. Your IT or security team should determine whether a browser policy exception is required.

See Configure Local Network Access for Kaltura eCDN for affected environments and configuration options.

Was this article helpful?