Skip to main content
SCAIRE

Proxmox

Manage hypervisor SSH connections (the table below) and provisioning credentials.

Configured Servers

Each row is one Proxmox hypervisor. The primary server is the live SSH target agents connect to. Its host, port, and host-key details sync automatically to the flat config keys.

Primary: 192.168.1.34:22 1 enabled / 1 total
Name Host Status Actions
PVE1 Primary 192.168.1.34 Enabled

Provisioning Credentials

One-time bootstrap SSH credentials used by the setup wizard to create per-agent SSH users, keys, and sudoers on the hypervisor.

Root or sudo-capable admin used for one-time bootstrap

Path to root SSH private key

Insights

Servers
1
1 enabled
Primary Target
192.168.1.34:22
PVE1
Host Key
None
strict
How SSH Targeting Works

The primary server is the live SSH target that all four agents (Faire, Grian, Saor, Nasca) connect to for diagnostics. Its host, port, and host-key fingerprint sync automatically to the flat config keys agents read at boot.

Only one server is primary at a time. Setting a new primary demotes the old one. The primary must be enabled for agents to function.

Provisioning Credentials

Provisioning SSH User and Key Path are one-time bootstrap credentials used by the setup wizard to create per-agent SSH users, keys, and sudoers on the hypervisor.

After provisioning, agents connect using their own dedicated SSH users (not the root key). The root key is never used for routine diagnostics.

The key path points to a private key file on disk. SCAIRE reads it at runtime, never embeds it in code or config.

Host Key Pinning

Strict rejects any mismatch between the stored fingerprint and the server's actual key. Safest against MITM.

TOFU (Trust On First Use) accepts the key on the first connection, then pins it. Good for initial setup when you do not have the fingerprint yet.