The engine needs its own ports reachable, so the installer manages the host firewall for you. This page explains what it changes, which ports to open, and what to watch on a shared or cloud host.
The installer takes over the host firewall. On install and on updates it stops and disables firewalld, UFW, nftables, netfilter-persistent, iptables and ip6tables so the engine ports are reachable. Clearing those rules can also drop filtering and NAT that other software on the host relies on.
Ports the engine uses
Open these to the engine on each host. The control panel runs on the master; media delivery runs on every node.
| Port | What it is for | Reachable from |
|---|---|---|
| 22 / TCP | SSH — admin access, and the master installs and syncs each node over SSH | Your admin IPs; on slave nodes also from the master |
| 80 / TCP | HTTP — control panel (master) and media delivery (HLS, DASH, TS); also Let’s Encrypt HTTP-01 | Admins and viewers |
| 443 / TCP | HTTPS — the same control panel and media over TLS | Admins and viewers |
| 1935 / TCP | RTMP — publish in and play out | Publishers and players |
| 4327 / TCP | Database (bundled MySQL) — in a cluster the slave / edge nodes read the master’s database | The master, from the slave nodes. Localhost-only on a single server |
| 8443 / TCP | Cluster control channel — the master’s encrypted RPC over WebSocket; nodes connect to it | The master, from the slave nodes |
The panel itself runs behind the built-in web server on 127.0.0.1:8080 — that is internal and does not need opening. On a single server, only 22 / 80 / 443 / 1935 need to be reachable from outside; 4327 and 8443 stay on localhost. In a cluster, the master must also accept 4327 and 8443 from your slave nodes.
Outbound. Allow outbound HTTPS (443) so the engine can reach licensing, the software-update feed, the IP geolocation databases and your EPG sources.
What is left behind
- Saved rule files stay on disk — they are not deleted, just not enforced.
- Custom firewall scripts and cloud or provider firewalls are not managed by the engine.
- A later rollback does not restore the previous firewall state.
On a shared host, review your network policy before installing or updating. If you run a cloud firewall or security group, open the engine ports there yourself.
Check what is listening
# ports the host is listening on
sudo ss -tlnp