Skip to content

FAQ

Is NexoVirt installed on my Proxmox nodes?

Section titled “Is NexoVirt installed on my Proxmox nodes?”

No. NexoVirt runs on its own management server and talks to Proxmox over the API, plus a small, constrained on-host agent. Your Proxmox install is never replaced or modified beyond that agent.

Yes, that is the point. The dashboard and guest list are panel-wide across every connected host, with no host picker: guests, nodes, and activity from every host show up together.

Do I need the on-host agent for everything?

Section titled “Do I need the on-host agent for everything?”

No, but it is required for most of the interesting parts: guest provisioning (create/reinstall/delete), NAT and port-forwarding, firewall inspection, cloud-image downloads, and Ansible automation all go through it. Read-only inventory and metrics collection work over the Proxmox API alone. See Hosts & onboarding.

A fresh Ubuntu 22.04 or 24.04 server, as root. See Installation.

No. The first install is IP-only over HTTP; you add a hostname and TLS later from Settings → Domain in the panel, or with the domain:apply CLI equivalent. See Installation.

Re-run the same installer command: it detects the existing install, updates in place, and runs any pending database migrations automatically. Your hosts, users and data are preserved. See Installation.

What if I misconfigure my domain and lock myself out?

Section titled “What if I misconfigure my domain and lock myself out?”

Run php spark domain:reset as root, locally on the server. It restores IP-only access (resets domain.allow_ip, the base URL, and the HTTP catch-all vhost) so you can fix the hostname/TLS setting from inside the panel again. See the CLI reference.

What’s the difference between Community and Enterprise?

Section titled “What’s the difference between Community and Enterprise?”

Community Edition is free, self-hosted, and includes every feature in the panel, capped at 2 Proxmox nodes with unlimited VMs and containers on them. Enterprise lifts the node cap and adds white-label branding and priority support; everything else is identical. See Editions & licensing.

What happens if my license expires or I go over the node cap?

Section titled “What happens if my license expires or I go over the node cap?”

The panel degrades to Community Edition limits rather than breaking. Over-limit installs see a banner and new hosts/guests are soft-blocked (coded NX-EDITION-0001/NX-EDITION-0002, see error codes) until you remove hosts or upgrade: nothing already running is stopped or deleted.

Do I need to be online for the license to keep working?

Section titled “Do I need to be online for the license to keep working?”

The license verdict is cached locally and re-checked periodically (license:check); the panel reads the cached result on every page load rather than calling out on each request.

It is a small, constrained dispatcher installed via SSH during onboarding. It only accepts an allowlisted set of jobs (writing cloud-init snippets, ensuring the managed image storage, downloading and deleting images, applying NAT rules, reading system/firewall state, running Ansible), each host-side validated, and reports back over a heartbeat. It is not a general remote-shell backdoor.

Can I remove the agent without losing my host?

Section titled “Can I remove the agent without losing my host?”

Yes. Remove agent on the Hosts page uninstalls the agent service from the node but keeps the host, its inventory, metrics, and the nexovirt-images storage, so you can re-onboard in one click later. A full host delete wipes everything for that host, including the agent.

Why is the panel blocking me with an “update the agent” screen?

Section titled “Why is the panel blocking me with an “update the agent” screen?”

The agent is mandatory and version-pinned: if any active host’s agent is missing, has gone stale (no recent heartbeat), or is running an older version than the panel expects, a non-dismissible modal walks you through updating it in place, with no separate SSH session required beyond the one it opens itself.

Backups integrate with Proxmox Backup Server (PBS): attach a PBS server, browse its datastore and snapshots, run garbage collection/verify, and configure scheduled prune (retention) policies evaluated hourly by pbs:prune. See Backups (PBS).

Yes, separately: backup:run builds a full panel backup (database dump plus uploads/images) and pushes it to a configured destination, enforcing retention. It is off by default (backup.enabled) and runs daily via cron once enabled.

Looking for the REST API? It has its own interactive reference with every endpoint, generated from the panel’s live OpenAPI schema rather than hand-written here. For CLI commands and their exact schedule, see the CLI & daemons reference; for what a specific error code means, see Error codes.