Edge Nodes

An edge node is a server that stands between viewers and your origin. The gateway sends viewers to it by rewriting redirects, so a stream that would have come from the origin host comes from the node instead. Nodes belong to one server and are managed from that server's panel under Edge Nodes.

There are two kinds:

Managed — you give the dashboard the box's IP and root password, and it installs the Proxima edge agent over SSH. The agent enrolls, reports in every 15 seconds, and receives its port rules from the dashboard.
External — your own proxy, such as an NGINX box you already run. The dashboard stores only a name and IP and never touches it.

Add a managed node

Open Edge Nodes in the server's panel and click Add node.
Enter a name, the public IP, and the root password. Ubuntu 22.04 and 24.04 are supported.
Click Install. You watch the steps live: connect, check root, upload the installer, install and enroll. The node shows Online as soon as its first heartbeat arrives.

The node starts with the server's port template, so it already listens on the same ports as your gateway and forwards each to the matching origin port. You can edit the rules on the node's page.

Add an external node

Click Add node, choose External, and enter a name and IP. It is usable right away. Nothing monitors it, so it always counts as online.

Use a node

Anywhere a rule takes a destination, the picker offers your nodes:

Geo URL replacements and ASN URL replacements, per origin host.
CDNs, to pool several nodes behind one destination with weights and automatic skipping of offline nodes.
Traffic routes, to send a whole country or network to a node or CDN.

The port, path and query of the redirect are kept, so the node must listen on the same port as the origin host it replaces. The port template takes care of that for managed nodes.

Status and health

Managed nodes report in every 15 seconds. A node that misses three reports shows Offline, and CDNs stop sending viewers to it until it comes back. A node that was added but never installed shows Pending.

Connection limit

Each managed node can carry a connection limit. Once the node is full, new viewers are redirected straight to the origin instead, and viewers already streaming are not interrupted. The destination picker stops offering a node that is at 90% of its limit, and its counters turn amber.

Capacity and host checks

The node page shows live CPU, CPU pressure, and megabits per viewer, with a history chart for the last 48 hours. Pressure is the number to watch: it rises before viewers start buffering.

The agent also grades the host on startup and every few minutes for the settings that measurably cost streaming capacity, such as running inside a VM, a single-queue network card, or a powersave CPU governor. Each warning comes with a fix. The agent only reports; it never changes host settings.

Remove a node

Delete the node from its page. Point any rule or CDN that used it somewhere else first; the dashboard tells you where it is still referenced.