Getting started

The first time you open Proxploy, it walks you through a four-step wizard. Server state decides which step you’re on; reloading mid-wizard picks up where the server thinks you are, not where the page last rendered.

1. Admin account

Email, display name, and a password of 12 or more characters. This creates the first user and logs you in immediately.

If you’ve already configured an OIDC identity provider in Settings, the login page shows a Sign in with SSO button instead. An OIDC login for someone without an existing Proxploy account provisions one automatically from the verified identity token.

2. First host

Add your first Proxmox host, or skip this step; it’s entirely optional at this point. A host can be added later from Settings, and everything in Proxploy except managing a node works without one connected. See The minimal-privilege API token for what adding a host actually needs from you.

The wizard generates a pveum script for exactly the capabilities you choose: monitoring (always required), lifecycle, console, backup, and node power. Each gets its own privilege-separated token so no single token carries more than it needs.

3. Authorize installs (optional)

If you added a host and it generated an SSH key for it, this step shows you the exact line to add to /root/.ssh/authorized_keys on that node, and a button to verify Proxploy can now reach it. This step only appears when a host needs SSH authorization; see SSH key enrollment for what this key is for and why it’s optional.

If a mis-pasted line causes verification to fail, the wizard tells you so directly, rather than surfacing a confusing error the first time you try to install something. If the node’s SSH host key doesn’t match what was seen before, the wizard stops and tells you to investigate; a changed host key is treated as a security event, not a retry.

4. Done

Whether or not you added a host, the wizard finishes here and takes you to the Cluster view, Proxploy’s main screen.