Skip to content

Add a Proxmox VE node

VirtConsole manages Proxmox VE nodes without installing the agent. The panel talks to the Proxmox API directly. Proxmox VE 8 and 9 are supported.

  • A working Proxmox VE 8 or 9 node, reachable over HTTPS from the management server.
  • An API token from the Proxmox web interface: Datacenter > Permissions > API Tokens > Add. You need the full token in the form user@realm!tokenid=UUID.
  • The management server installed.

In the admin panel go to Infrastructure > Hypervisors.

  1. Click Add hypervisor. The Add hypervisor dialog opens.
  2. Select Proxmox VE as the connection type.
  3. Fill in the fields:

Fields

Field What to enter Example
Name A label you recognise in lists. pve-us-east-1
IP Address The address the panel uses to reach the Proxmox API. 203.0.113.20
Group The hypervisor group this node belongs to. The first Proxmox node in a group turns the group into a Proxmox cluster automatically. US-East
Node Name The node’s name exactly as Proxmox knows it. pve1
API Token The full token string from Proxmox. root@pam!virtconsole=1b4d6a2f-…
Fingerprint (optional) The node’s TLS fingerprint, to pin the certificate. leave empty
  1. Click Link Proxmox Node. The dialog closes and the node appears in the hypervisors list.

The panel connects to the Proxmox API, reads the node’s storage, networks and existing guests, and the node shows as online. Add more nodes to the same group to grow the cluster; no separate cluster setup is needed in VirtConsole.

  • Authentication failed. The API token string is incomplete. Paste the full user@realm!tokenid=UUID value from Proxmox.
  • The node stays offline. The Proxmox API (port 8006) is not reachable from the management server, or the TLS certificate fails validation. Add the fingerprint if you use a self-signed certificate.