Add nodes

About 5 min

A node is the machine that carries visitor traffic. Once the controller is installed, get a command in the panel and run it on the new machine. After you approve it, the node fetches its configuration and comes online.

Demo
Step 1 / 5
Get the command

The token is one-time and valid for 30 minutes; one command installs one node

Node Management+ Add NodeCopy command
Step 2 / 5
Pre-checks

Run as root; every problem is listed at once and the installer exits without changing the machine

# paste the whole command you just copied
Step 3 / 5
Verify and install

Downloads the node package and verifies the signature; a bad signature is always refused

Step 4 / 5
Installed

The node ID is shown on screen

NODE_INSTALL_DONE <version>
Step 5 / 5
Approve

Initialize it; within seconds it gets its certificate, pulls its config and starts services

Node ManagementInitialize
Shows as Online in the node list
Node → controller7443 · 7444 · 7445
Open to visitors80 / 443
Command validity30 minutes
Get the command → run it on the new machine → approve, and the node comes online by itself

Requirements

  • Debian 12 / 13, or Ubuntu 24.04 / 26.04 and later, x86_64 or arm64, with systemd; run as root.
  • A clean system: no pre-installed nginx / OpenResty, and ports 80 and 443 must not be taken by other programs.
  • The node can reach ports 7443 (node communication), 7444 (upgrade package delivery) and 7445 (log ingest) on the controller, and opens the ports it serves (usually 80 / 443).
  • Do not install it on the controller machine.

Get the command

Go to the Node Management page, click + Add Node in the toolbar, and click Copy command in the dialog. The token in the command is one-time and valid for 30 minutes; one command installs one node.

Run it on the node

Paste and run it as root on the new machine. The installer runs pre-checks first: if anything fails, it lists every problem and exits without changing the machine. After that it downloads the node package and verifies the signature; a bad signature is always refused. When no version is given, the default version for new installs (latest) on the materials site is also used only after it passes the superadmin signature check; otherwise the script exits without installing. The last line NODE_INSTALL_DONE <version> means it is installed, and the node ID is shown on screen.

Tip Running it right after getting the command is fine: the controller allows the node automatically, and the script waits up to 3 minutes, retrying every 5 seconds.

Approve

Back on the Node Management page, a banner at the top reads “New server installed, waiting to be initialized”; click Initialize to approve it (if several are waiting, click Review and handle to open the drawer, then click Initialize on each). You do not need to log in to the node again: within seconds it gets its certificate, pulls its config and starts services, and shows as Online in the node list.

Caution If the controller address in the command is a local or private address, two # 【警告】 warning lines appear before the command. First set the node communication address under System Admin › Upgrade & Maintenance › Node Communication and get the command again; otherwise nodes elsewhere probably can't reach the controller.

FAQ

  • Token expired: click Add Node again for a new command.
  • Interrupted halfway: re-run the same command. Finished steps are skipped and missing ones filled in; the node identity stays the same.
  • Clock not synchronized: the script warns you; once online, the node corrects its clock against the controller every 10 minutes. If your network blocks UDP 123, open it.
  • Taking a node out: see Uninstall and migrate.
Get started

Try the live demo

Open the live demo, or contact us for a quote and the install command