CDNCA
Browse all docs

Node reinstall guide

Node reinstall guide: generate the command in the console, purge the old state, install again; configuration and certificates are then redelivered.

What it does

Reinstalls an already connected node on a new machine, or on a machine whose system was reset. The node keeps its ID, name, region, IP, line group and site assignments, so the control plane needs no changes; site configuration and certificates are delivered again automatically and nothing needs to be rebound by hand.

When to use it

  • You are moving the node to a new machine.
  • The machine hosting the node had its system reset and the node must be installed again.

Where to configure it

In the console: the node list, select the node, "Reinstall this node". The page generates a one-time command; "Command validity" defaults to 3600 seconds (1 hour), the command can be used once, and an expired one is generated again.

Steps

  1. In the console click "Reinstall this node" and copy the generated command.
  2. If you are reinstalling on the same machine, first uninstall and purge the old state as root (not needed on a brand new machine):
/usr/libexec/cdnca-edge-agent/uninstall.sh --purge --non-interactive --confirm-purge DELETE-EDGE-IDENTITY-AND-STATE
  1. On the machine that takes over the node, run the command copied in step 1 as root. When the install finishes, the Agent certificate on the original machine is revoked and it disconnects.
  2. Back in the console, confirm the node is online and its configuration is delivered. For nodes in the same line group, do one at a time.

The purge also removes the dynamic routing state. If another disk is mounted under /var/lib/dynroute, its contents are kept and you are told so; everything else is removed as usual.

What happens automatically afterwards

  • Site configuration is delivered again; if a delivery fails, it is retried every 10 minutes for 6 hours.
  • The wait for certificate issuance is reset, and the next round (about 1 minute) delivers them.
  • Once the certificates reach all nodes, the console shows the publication as succeeded.
  • The control plane updates the node installation package periodically, so a reinstalled node gets the version matching the control plane. When the control plane's preferred entry is WebSocket, the reinstall command also carries direct-connection parameters, and falls back to WebSocket on 443 if the direct connection fails.

FAQ

The command failed halfway

Fix the cause and run the same command again with --resume added. If the token failed before registration it can be reused within 1 hour.

The command expired

Go back to the console and click "Reinstall this node" again for a new command.

The node is online after the reinstall but the site does not open

Wait one round of automatic redelivery. If it still does not open after a while, check the node's publication status in the console and whether the certificates have arrived.

Do other nodes need reinstalling too

No, reinstall only the node that has the problem. When several nodes of a line group need it, do them one at a time.