Guide · For administrators
Nodes
A node is a server with Incus. VPSs are created on the node with the most free RAM, unless you choose one.
Connect a node
- On the server, if the Incus API is not listening on the network yet, enable it:
incus config set core.https_address :8443
- Create a token for the panel and copy it whole:
incus config trust add koavm
- In Nodes › Add node paste the token, name the node (e.g.
gra-01) and pick its city on the map.
The token contains the server certificate's fingerprint: the connection is encrypted and verified. The advanced options let you change the address, the VPS bridge (default br-vps) and the storage pool (default default).
The panel's SSH key
For some tasks the panel logs into the node over SSH: migrations, backups stored on a node, IPv6 setup. Add the panel's key (shown on the Migration page) to the node's /root/.ssh/authorized_keys, or to a user with passwordless sudo, and set user and port on the same page. The Test button checks that it works.
Status and resources
For each node you see CPU, assigned and used RAM, used and assigned disk, running VPSs. The panel reads the nodes every 30 seconds; Refresh reads them right away. A node that does not answer is shown in red with the last error.
Maintenance and disconnecting
- Enter maintenance: no new VPSs are created on the node; existing ones keep running.
- Disconnect: only possible with no VPSs on the node. The panel also removes its own certificate from the server.
Provider nodes
If the server belongs to OVHcloud, Hetzner, Contabo or Scaleway (Dedibox) and you connected the provider account, the node is recognised by its main IP and its additional IPs become available for VPSs. See Network and IPs.