LK Wood IV

Posted on Jul 4 • Originally published at techfuelhq.com

How to Install Proxmox VE (2026): Install + Update Reference

#homelab #proxmox #selfhosted #tutorial

Installing Proxmox VE is genuinely easy. The graphical installer is a few screens, and it writes itself to disk in a couple of minutes. What trips people up is not the install itself: it is the first fifteen minutes afterward, where a default install points at a repository you cannot use without paying, and the longer-term question of how you keep the thing updated once it is running.

This is the generic reference for both. It is hardware-agnostic on purpose: the steps below apply to a mini PC, a used office desktop, an old gaming rig, or a rack server. If you want a hands-on, click-by-click walkthrough on a specific small box, the Proxmox mini PC setup guide is the hardware-specific companion to this one. If you are still choosing hardware, start with the Proxmox hardware requirements. And if you already run VE 8 and want to jump to VE 9, that is a different, planned operation covered in the 8-to-9 upgrade gotchas.

Everything below is cited to the official Proxmox documentation. The current release as of this writing is Proxmox VE 9.2-1 (released May 21, 2026), built on Debian 13 "Trixie." If a command or file path is here, it is real and current for VE 9.

Part 1: The clean install (any hardware)

Step 1: Download and verify the ISO

Grab the latest Proxmox VE ISO from the official downloads page. As of June 2026 that is the VE 9.2-1 installer, about 1.7 GB.

Do not skip the checksum. The download page publishes a SHA256 value next to the ISO. After downloading, compute the hash and compare it to that published value:

# Linux / macOS
sha256sum proxmox-ve_9.2-1.iso

# Windows (PowerShell)
Get-FileHash proxmox-ve_9.2-1.iso -Algorithm SHA256

If the two strings do not match, the download is corrupt or tampered with. Delete it and re-download. This takes ten seconds and it is the one verification step that matters before you write installation media.

Step 2: Write the USB installer

A USB stick is the standard install medium. The tool depends on your OS, and the official guidance is specific about which ones work:

Linux: use dd. Identify the USB device first with lsblk, then write with dd bs=1M conv=fdatasync if=./proxmox-ve_9.2-1.iso of=/dev/XYZ (replace /dev/XYZ with your actual USB device; getting this wrong overwrites the wrong disk).
Windows: Etcher works with no configuration. Rufus also works, but you must select DD mode when it prompts, not ISO mode.
macOS: convert the ISO to a raw image, then write it (see the official media-prep page for the exact hdiutil and dd sequence).

One specific warning from the docs: do not use UNetbootin. It is incompatible with the Proxmox installer.

Step 3: Boot the installer and pick your filesystem

Plug the USB into the target machine, power on, and bring up the boot menu (commonly F11, F12, or Del). Select the USB device, then choose Install Proxmox VE.

Two decisions matter. Target disk and filesystem: select the SSD or NVMe you want Proxmox on, and be careful not to pick the USB installer drive by accident.

Filesystem	When to choose it
ext4 (default)	Single-disk machine. Simple, fast, reliable, uses an LVM-thin pool Proxmox manages natively. The right first-install answer.
ZFS	Two or more drives and you want a mirror or RAID-Z, plus snapshots, checksums, and self-healing. Wants meaningful RAM for its cache.
XFS	Offered with LVM, but far less common in Proxmox setups than ext4.
Btrfs	A technology preview. Not recommended for a production-style install yet.

The official installer note is blunt that ZFS on top of any hardware RAID is unsupported and can cause data loss, so if you run ZFS, give it the raw disks. For a first build on one drive, choose ext4 and move on.

Network and password: set a hostname, then set a static IP outside your DHCP range so the web UI always lives at the same address. Set a strong root password. The installer builds a Linux bridge called vmbr0 on your first NIC so VMs and containers can reach the network. Click install; it writes to disk in a few minutes and reboots.

Step 4: Reach the web interface

Point a browser on another machine at the IP given during install, on port 8006:

https://your-ip:8006

Note the https and the :8006. Plain http or a missing port is the single most common "it didn't work" mistake, and the install is almost certainly fine. You will get a certificate warning because Proxmox uses a self-signed cert; accept it and log in as root.

Part 2: The first fifteen minutes (the repository fix)

This is the part generic install guides skip, and it is the one step every Proxmox install needs. A fresh install points apt at the enterprise repository, which requires a paid subscription. Without a key, every apt update ends in 401 Unauthorized and your package lists never refresh.

Proxmox VE 9 also changed the repository file format to the deb822 .sources format, so the files look nothing like the one-line sources.list entries from VE 8.

Disable the enterprise repository

Open the node shell (web UI, your node, Shell) and edit /etc/apt/sources.list.d/pve-enterprise.sources, adding a single line so it reads Enabled: no. That suppresses the enterprise repo without deleting it.

Enable the no-subscription repository

Create the no-subscription sources file with the exact deb822 contents the docs publish for VE 9:

# /etc/apt/sources.list.d/proxmox.sources
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg

You can do all of this from the web UI instead: node, Updates, Repositories, Add, pick No-Subscription, then highlight the enterprise row and click Disable. The GUI writes the same files for you.

The no-subscription repo ships the same packages as enterprise without a key. Proxmox is explicit that these are "not always as heavily tested and validated," so it is fine for a home lab but is not their recommendation for production.

Run the first update

apt update
apt full-upgrade

Use full-upgrade, not plain upgrade, more on why in Part 3. Reboot if a new kernel was installed. The subscription-nag popup at login is cosmetic; click OK and move on.

Part 3: How to update Proxmox over time

Once Proxmox is running, "update" means two very different things, and conflating them is where homelabs get into trouble.

Routine updates (within a major version)

Normal maintenance, keeping VE 9 current as point releases ship (9.1 to 9.2). From the shell, apt update then apt full-upgrade; or in the web UI, select the node, open Updates, Refresh, then Upgrade.

Why full-upgrade and not apt upgrade? Plain upgrade refuses to install anything that requires a new dependency, and on Proxmox that means the kernel and the pve-manager stack get held back, exactly the packages you want updated. full-upgrade installs them. A reboot is only needed when a new kernel arrives.

Major upgrades (across major versions)

Moving from VE 8 to VE 9 is a different animal. It crosses to a new major version, which moves the underlying Debian base and kernel, and it carries real breaking changes: LVM autoactivation defaults change, network interfaces can be renamed, and PCI passthrough can need attention. That is a planned event with its own pre-flight checklist: back up first, run the pve8to9 --full checker, pin your NIC names, and have console access that is not the web GUI. The full procedure is in the Proxmox VE 8 to 9 upgrade guide. VE 8.4 gets security and bug-fix updates until August 2026, so there is no pressure to rush.

Common install gotchas

apt update returns 401 Unauthorized. You are still on the enterprise repository. Disable it and enable pve-no-subscription (Part 2). This is the number-one new-user issue.
The web UI will not load. You used http instead of https, or forgot :8006. The correct URL is https://your-ip:8006.
VMs will not start ("KVM not available"). Hardware virtualization (Intel VT-x or AMD-V) is disabled in the BIOS/UEFI. Reboot into firmware and enable it, plus IOMMU (VT-d / AMD-Vi) if you plan passthrough.
You picked ZFS and the host feels short on RAM. ZFS reserves RAM for its cache. Size it deliberately.
You accidentally installed onto the USB stick. Always confirm the target disk in the installer is your internal SSD/NVMe.

After the install: what to build

For a screen-by-screen walkthrough on a specific small machine, follow the Proxmox mini PC setup guide.
For each service, decide between a container and a full VM. The LXC vs VM in Proxmox guide has the decision tree.
To size your box, how many VMs and containers your RAM and cores can support with ZFS overhead included, the Proxmox capacity planner does the math.

The install is the easy part. The repository fix is what makes updates work, and knowing the difference between a routine update and a major upgrade is what keeps the box healthy for years.

Sources

Originally published at techfuelhq.com.

DEV Community