Frequently asked questions
Frequently asked questions about installing, running and licensing NexoVirt, with short answers and links to the full guides.
General
Section titled “General”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 agent on each connection. Your Proxmox install is never replaced; the agent only runs an allowlisted set of jobs.
Can I manage more than one Proxmox host?
Section titled “Can I manage more than one Proxmox host?”Yes, that is the point. The dashboard and guest list are panel-wide across every connected host and cluster, with no host picker: guests, nodes and activity from every connection show up together.
Do I need the node agent?
Section titled “Do I need the node agent?”Yes. The agent is mandatory and version-pinned: the panel shows a blocking notice until every connection has a healthy agent at the current version. Guest provisioning, image downloads, NAT and port-forwarding, firewall inspection, the WireGuard VPN, DynDNS and node system updates all go through it. See The node agent.
Install & update
Section titled “Install & update”Which OS do I install it on?
Section titled “Which OS do I install it on?”A fresh Ubuntu 22.04 or 24.04 server, as root. Debian works on a best-effort basis. See Requirements and Installation.
Do I need a domain to start?
Section titled “Do I need a domain to start?”No. The first install is IP-only over HTTP; you add a hostname and TLS later under Settings → Domain. See Installation.
How do I update?
Section titled “How do I update?”From the panel, or let bug-fix releases install themselves. Every update is signature-verified, takes a backup first and rolls back code, configuration and database if anything fails. Your hosts, users and uploads are preserved. See Updates.
What if I misconfigure my domain and lock myself out?
Section titled “What if I misconfigure my domain and lock myself out?”Run nexovirt-domain reset as root on the server. It restores plain IP access over HTTP so you can fix
the hostname or TLS setting from inside the panel again. See the
CLI reference.
Editions & licensing
Section titled “Editions & licensing”What’s the difference between Community and Enterprise?
Section titled “What’s the difference between Community and Enterprise?”Community Edition is free and self-hosted, capped at 2 Proxmox nodes with unlimited VMs and containers, and includes every core feature. The paid plans (Pro, Business, Unlimited; shown as Enterprise in the panel) raise the node cap and add commercial features such as white-label branding, event webhooks, single sign-on, team roles and the reseller tier. 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 adding nodes or guests is refused (coded NX-EDITION-0001/NX-EDITION-0002, see
error codes) until you remove nodes or upgrade. Nothing already running is
stopped or deleted, and white-label branding reverts to the defaults.
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 panel re-validates the license every 5 minutes (license:check). The signed license token is
checked locally on every page and stays valid offline for up to 14 days, so a short outage of your
internet connection or of the license service changes nothing.
Do I need a license key to install?
Section titled “Do I need a license key to install?”No. The installer registers a free Community license automatically. You can claim the install to your NexoVirt account later from Settings → Edition & license (needed for DynDNS, for example).
The agent
Section titled “The agent”What does the node agent actually do?
Section titled “What does the node agent actually do?”It is a small dispatcher installed over SSH during onboarding. It only accepts an allowlisted set of jobs (cloud-init snippets, the managed image storage, image downloads, NAT and VPN rules, firewall and system reads, DynDNS updates, package updates), validates every job on the node and reports back over a heartbeat. It is not a general remote shell.
Can I remove the agent without losing my host?
Section titled “Can I remove the agent without losing my host?”Yes. Remove agent uninstalls the agent service but keeps the host, its inventory, metrics and the
nexovirt-images storage, so you can re-onboard in one click later. Deleting a host is a full wipe,
agent included.
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?”If any active connection’s agent is missing, has stopped sending heartbeats, or runs an older version than the panel expects, a blocking dialog walks you through Set up agent or Update agent in place. It closes on its own once the agent reports in at the current version. A host the panel has detected as down is left out of this check, so you can still reach the failover page.
Backups
Section titled “Backups”Does NexoVirt back up my Proxmox guests?
Section titled “Does NexoVirt back up my Proxmox guests?”Backups integrate with Proxmox Backup Server (PBS). PBS storages already configured on your nodes are discovered automatically. You can browse backups, restore as a new guest, restore single files, run garbage collection and verify, and schedule prune (retention) policies. See Backups (PBS).
Does NexoVirt back up itself (the panel)?
Section titled “Does NexoVirt back up itself (the panel)?”Yes, separately: Settings → Backups builds a panel backup (database dump plus uploads) on a daily schedule and pushes it to local storage, FTP or SFTP with retention. It is off until you enable it.
More questions
Section titled “More questions”Looking for the REST API? It has its own interactive reference with every endpoint, and Automation (REST API) walks through a typical workflow. For CLI commands and their schedule, see the CLI & daemons reference; for what a specific error code means, see Error codes.