Still on Proxmox VE 8? It is out of support: how to upgrade to Proxmox VE 9 safely
Proxmox VE 8 stopped receiving security updates on 31 August 2026. If your home server still runs it, here is a calm, step-by-step route to version 9, using the official checklist tool and with a backup plan if anything goes wrong.
By OwnYourStack Admin · Published
Proxmox VE 8 arrived in June 2023 on Debian 12 “Bookworm”. Its standard support ended on 31 August 2026: no more security patches, no bug fixes. Any new vulnerability in the hypervisor, its kernel or its bundled components now stays open on version 8 machines, which is a poor place to be for a box that often runs your router VM, your password manager and your backups.
The replacement, Proxmox VE 9, has been available since August 2025 and is now at version 9.2 (May 2026), built on Debian 13 “Trixie” with Linux 7.0. Recent point releases also include fixes for a string of Linux kernel privilege-escalation flaws disclosed during 2026.
Option 1: a fresh install
If your server is simple, a clean install of 9.2 and restoring your VMs and containers from backup is often the least stressful route, and it leaves you with a tidy system. It requires a working backup of every guest (ideally on Proxmox Backup Server or an external disk) and a note of your network and storage configuration.
Option 2: an in-place upgrade
Proxmox supports upgrading in place with apt. It is reliable if you follow the official procedure carefully. Here are the stages, with the official wiki as your reference throughout.
1. Get to the latest Proxmox VE 8
Fully update the node first. Running pveversion should show pve-manager 8.4.x; the upgrade path starts from there.
2. Back up, and test a restore
Back up every VM and container to storage that is not on the node itself. Also keep a copy of the configuration in /etc/pve, /etc/network and /etc/apt. If your root filesystem is on ZFS, a snapshot just before the upgrade gives you a quick way back.
3. Run the checklist tool
Proxmox ships a script called pve8to9. Run it with the --full option and fix every failure it reports before going further, then run it again until it comes back clean. A common failure on home servers is the systemd-boot meta-package being installed; the wiki explains how to remove it safely.
4. Handle the add-ons first
If you run Ceph, it must be upgraded to Ceph Squid (19.2) before the Proxmox upgrade. If Proxmox Backup Server is installed on the same machine, upgrade it to version 4 first.
5. Switch the repositories to Trixie
Change every Debian and Proxmox repository entry from bookworm to trixie, including the Proxmox no-subscription or enterprise repository. Proxmox VE 9 uses the newer deb822 .sources format; the wiki’s repository section shows the exact files to create.
6. Run the upgrade
Do this from a console that will survive a dropped connection (the physical console, IPMI, or a tmux session), since SSH can disconnect during the upgrade. Run apt update then apt dist-upgrade. When asked about modified configuration files such as /etc/issue, keeping the installed version is generally the safe answer unless the wiki says otherwise.
7. Reboot and verify
Run pve8to9 --full once more, reboot (mandatory, even if you were already on a recent kernel), then check that every guest starts and that the web interface reports version 9. In a cluster, upgrade one node at a time and migrate guests away first.
What you gain
Beyond security updates, Proxmox VE 9.2 brings a dynamic load balancer for clusters, WireGuard as a software-defined networking fabric, management of custom CPU models from the interface, and an HA “arm/disarm” switch for maintenance. For a single home server, the security support alone is reason enough.
