Which Proxmox versions does AtlasPVE run on?

AtlasPVE runs on Proxmox VE 8 and Proxmox VE 9. A single host and a node in a cluster are both supported. The installer checks the machine before it starts; if a condition is missing, it stops without writing anything and states the reason.

Supported versions

Proxmox VE 9

Based on Debian 13 trixie.

Proxmox VE 8

Based on Debian 12 bookworm.

AtlasPVE is tested on freshly installed Proxmox VE 9 and Proxmox VE 8 machines.

Proxmox VE 7 and earlier are not tested and not supported. Proxmox ended support for the 7 series in 2024.

What is required

An x86_64 processor

AtlasPVE components are packaged for x86_64 only; the installation does not start on ARM.

systemd

AtlasPVE services run as systemd units. systemd is always present on Proxmox VE.

A free port 19191

The panel opens on this port. If another process holds the port, the installation does not start.

A writable /etc/pve

Certificate and node information is read from the Proxmox cluster file system. If this directory is not writable, the cluster file system is not running and the installation does not start.

Disk space

The space needed is calculated from the real size of the package, about 400 MB. If there is not enough space, the installation stops without leaving a partial copy.

Memory

If available memory is below 512 MB, the installation continues, but a note says the panel may run slowly.

What is not required

A permanent internet connection

The install command connects to the portal once to get the package and the license approval. The runtime and the monitoring services come inside the package. After installation, the internet is used only for product updates and the app catalog.

A Proxmox subscription

AtlasPVE works the same with subscription and no-subscription repositories.

A separate server or virtual machine

AtlasPVE is installed directly on the Proxmox host.

Node.js on the system

AtlasPVE brings its own runtime; if the machine has Node.js, it is not touched.

Pre-install check

Before the installation starts, each of the conditions above is checked. The result falls into two groups:

Blocking

Processor architecture, systemd, port 19191, /etc/pve, disk space. If even one is missing, the installer writes nothing to the machine.

Warning

Low memory, a locked package manager, name resolution not working, another service on port 443. The installation continues and the missing item is shown on screen.

If the installation stops, a copyable report is printed on screen. The report contains no secrets: version, architecture, kernel, Proxmox version and the failed checks. This report is added to a support request.

When a Proxmox update arrives

When a new Proxmox VE release comes out, AtlasPVE is first checked against it on its own test machines. Any change needed for compatibility comes with an AtlasPVE update. A Proxmox update does not remove AtlasPVE or delete its settings.

Frequently asked questions

Does AtlasPVE work with Proxmox VE 9?
Yes. Proxmox VE 9 and Proxmox VE 8 are supported and tested on both.
Can it be installed on Proxmox VE 7?
No. Proxmox VE 7 is not tested and not supported; Proxmox's own support for it also ended in 2024.
Can it be installed on a node in a cluster?
Yes. From the host it is installed on, AtlasPVE reads the cluster state, quorum and the other nodes.
Does it run on a machine with an ARM processor?
No. The components are packaged for x86_64 only; the installation does not start on ARM.
Is nested Proxmox, meaning Proxmox inside a virtual machine, supported?
Yes. AtlasPVE's own test machines are Proxmox installations running inside virtual machines.
Does the installation need internet access?
Once, during installation: the install command gets the package and the license approval from the portal. After installation the product works offline; the internet is used only for product updates and the app catalog.