Documentation
Getting started
Six steps, from an empty account to a running virtual machine. You need a Linux host inside the network where your Proxmox cluster lives, and root on that host.
Before you begin
- A Proxmox VE node or cluster, reachable over HTTPS from the host you are about to use
- A 64-bit x86 Linux host with systemd, on that same network, where you have root
- A template in Proxmox to clone machines from
Create an account
Sign up and you land in the panel with a trial already running. No payment details are asked for, and you can connect a host straight away.
Create an agent
In the panel, add an agent and give it a name that says where it lives, for example the site or the rack. The panel shows you an activation code once and never again, so keep it somewhere safe before you leave the page.
Install the agent on your host
The panel builds a one-line command containing a short-lived install link. Run it as root on the Linux host. It checks the architecture, downloads the binary, verifies the checksum against the platform, creates the service account and directories, fetches the licence file, enrolls, and starts the service under systemd.
shellcurl -fsSL https://app.provibr.com/api/install/<token> | shThe command asks for the activation code on the terminal rather than taking it on the command line, so the code never lands in your shell history or in a process list.Check that it came up:
shellsystemctl status provibr-agent journalctl -u provibr-agent -fWithin a few seconds the agent shows as online in the panel. If it does not, the service log on the host says why.
Get the TLS fingerprint of your Proxmox node
Provibr pins the certificate your Proxmox node actually presents. That is the node's own server certificate, not the certificate of the authority that issued it, and not a certificate from a reverse proxy in front of it. Run this from the agent host, so you are fingerprinting exactly what the agent will see:
shellopenssl s_client -connect pve.example.com:8006 </dev/null 2>/dev/null | \ openssl x509 -noout -fingerprint -sha256Copy the colon-separated hexadecimal value. The prefix that openssl prints in front of it is fine to include; the panel accepts it either way. If you replaced the node's certificate, take the fingerprint again, because a renewal changes it.You can also read the same value in the Proxmox web interface, under the node's System and then Certificates, on the entry for the node's own web certificate.
Connect the Proxmox integration
In the panel, add an integration, pick Proxmox VE and pick the agent you just installed. Fill in the host, the API token identifier, the token secret and the fingerprint from the previous step. The credentials are pushed once to that agent and sealed in its vault; the platform keeps only the field names.
The fingerprint is not optional in practice. Without it the agent cannot decide whether the certificate it is offered is yours, and the connection is refused rather than trusted blindly.After the integration reports as active, open its settings and set the node name, the storage and the range of machine IDs Provibr may use. An integration without a range cannot create anything, which is deliberate: the range is what keeps the panel away from machines you did not hand over.
Create your first machine
Add a plan with the cores, memory and disk you want, and point it at an address pool. Then create a server: choose the integration, the plan and the operating system to clone. The panel follows the clone task while it runs and the machine appears with an address from your pool already in its cloud-init configuration.
If something fails, the activity log on the server shows the reason the agent reported, in your own language, with the original message from Proxmox quoted underneath.