Hosts & onboarding

NexoVirt manages one or more Proxmox VE hosts or clusters from a single panel. This guide covers adding a host, onboarding the NexoVirt agent, the agent’s lifecycle, node management and inventory.

Adding a host

Add a host from the Hosts page with its address and Proxmox credentials.

Tip

The password is encrypted at rest and is never shown back to the browser or returned in any API response. Use the per-host Test action at any time to verify connectivity.

The NexoVirt agent

Provisioning and networking features (image downloads, NAT, firewall inspection) require a small agent running on each host. Onboarding it is one action from the panel.

1. Open the host and click Set up agent.
2. Provide a one-time root SSH credential. NexoVirt connects once over SSH, pins the host key, and installs a small systemd service.
3. The credential is discarded immediately after use, it is never stored unless you opt in.
4. The progress dialog shows each step live and waits for the agent’s first heartbeat.

Once onboarded, you can update or remove the agent in one click from the same page.

The agent is required and version-checked

If the agent is missing, stale, or running an older version than the panel expects, the panel shows a blocking notice on every page with a one-click fix. You can optionally store the SSH credential encrypted so future update/remove operations don’t re-prompt for it.

Agent safety

A fixed, validated job set: never arbitrary commands

The agent only ever runs a fixed, validated set of host-side jobs: staging an OS image, ensuring the managed image storage exists, writing a cloud-init snippet, applying NAT rules, reading the firewall. It never executes arbitrary commands sent from the panel, and every job’s inputs are validated host-side before it runs.

Node management

Each Proxmox node has its own management page in NexoVirt, reached from the dashboard’s node list or a host’s node table. It shows:

• Live CPU, RAM, network and storage charts.
• Tables of the node’s guests, storage volumes and networks.
• An “as of <timestamp>” marker so you always know how fresh the data is.

The page is backed by the database, not a live call to Proxmox, so it opens instantly and stays usable even if the host is temporarily unreachable. Admins can reboot or shut down the node from here (behind a typed confirmation) and open a root shell on the node itself.

Inventory

A per-host inventory job captures nodes, guests, storages and networks on a schedule and keeps a history, so you can see the current state and a storage-usage trend even when a host is offline.

• Offline guests keep their last-known IP address.
• Guests that have genuinely been deleted in Proxmox drop out of the inventory automatically.

Managed image storage

To support on-demand OS image downloads (see Guests), NexoVirt provisions its own nexovirt-images storage on every onboarded node, set up automatically as part of onboarding.

Next steps

• Create your first guest on a newly onboarded host.
• Set up IP zones and NAT for the host’s networks.
• Review the REST API for host-level endpoints.