Connect your Proxmox nodes

Before ProxDR can protect anything, it needs to reach the Proxmox cluster it manages. You do this on the Inventory page (“Add Proxmox Node”).

Two ways to connect

SSH (recommended — auto-provisions a token)

Give ProxDR SSH access to a node and it will provision its own scoped API token for you — no manual token juggling in the Proxmox UI. This is the quickest path.

You’ll provide:

• a name for the cluster/remote (e.g. prod-cluster);
• the node host/IP and SSH user (usually root);
• an SSH password or private key.

ProxDR connects over SSH, creates a dedicated API token, and stores it. From then on it talks to Proxmox over the API.

API token (bring your own)

If you’d rather create the token yourself in Proxmox, provide the token ID (user@realm!tokenname) and secret directly. Use this when SSH access isn’t available or your policy requires manually-scoped tokens.

Clusters vs single nodes

Point ProxDR at any node in a Proxmox cluster and it discovers the rest of the cluster automatically. A standalone node works too — it’s just a cluster of one.

Verifying

Once added, the node appears in Inventory with its nodes, guests, storage, and live CPU/RAM. If a connection fails, ProxDR surfaces the error so you can fix credentials or reachability. You can re-test a remote at any time.

Next: create a DR Site Pair so this site has somewhere to recover to.