How to Update Proxmox Manually

Knowing how to update Proxmox manually keeps you in control of when patches and kernel updates hit your server. This guide covers both the command-line and the web GUI approaches.

apt update
apt list --upgradable
apt dist-upgrade

I update manually, and only when Proxmox announces a new version or a significant security fix. Here’s exactly how I do it.

How to Update Proxmox via the Command Line

Connect via SSH or open a shell on your node, then run these three commands in order.

Step 1 — Refresh the package list

apt update

This checks the repositories for what’s available. Nothing gets installed yet. If you see a 401 Unauthorized error, as shown in the screenshot below, the enterprise repository is active without a subscription key. Run this to disable it:

To fix it, go to your node → Updates → Repositories, select the enterprise repository and click Disable, then run apt update again.

Step 2 — Check what’s waiting

apt list --upgradable

This shows every package with a pending update. Scan the list before committing. It tells you whether a kernel package is included. Look for names like proxmox-kernel-* or pve-kernel-*. If you see those, a reboot will be needed after the upgrade.

Step 3 — Apply the updates

apt dist-upgrade

Proxmox recommends dist-upgrade over plain apt upgrade. The reason matters: when multiple Proxmox packages update together, plain apt upgrade can hold some back due to dependency changes. dist-upgrade handles those correctly.

How to Update Proxmox via the Web GUI

If you prefer not to use the command line, the web GUI produces the same result.

Go to your node → Updates → click Refresh. Review the list, then click Upgrade. A console window opens and runs the equivalent of apt dist-upgrade.

If you see a 401 Unauthorized error, as shown in the screenshot below, the enterprise repository is active without a subscription key. Go to Repositories, disable the enterprise repo, add the no-subscription repo, then click Refresh again.

I use the command line because it’s faster and I can see exactly what’s happening — but either method works.

Do Your VMs Keep Running During an Update?

Yes. Running apt dist-upgrade does not interrupt your virtual machines or containers. They stay running throughout the entire update process. The only thing that interrupts them is a reboot and a reboot is only needed when a kernel package was part of the update.

This is one of those things nobody seems to state clearly, so update freely without shutting down your VMs first.

Do You Need to Reboot After Updating?

The most reliable way to check is to scroll through the apt dist-upgrade output. If you see any package containing pve-kernel-* or proxmox-kernel-*, reboot.

You can also try:

cat /var/run/reboot-required

But based on my own testing and feedback from the r/Proxmox community, this file is not reliably created on Proxmox after kernel updates. If the command returns nothing, do not assume a reboot is not needed. Check the upgrade output instead.

How Often Should You Update?

That depends on your setup. In my homelab, I update when Proxmox announces a new version, not for every individual kernel patch. The tradeoff is that some interim updates contain security fixes. If your server is internet-facing or exposed beyond your local network, staying closer to current makes sense.

For a homelab behind a firewall with no direct external exposure, the practical risk of waiting is low. The bigger risk is applying an update without checking what’s in it first — which is why I always run apt list --upgradable before committing.

Before running any update, make sure you have a current backup. If you haven’t set up Proxmox Backup Server yet, this guide walks you through it.

Related Articles

• How to Install Proxmox Server
• Proxmox Backup Server: What It Does and How to Set It Up

I’d love to hear from you — was this article helpful? Share your thoughts in the comments below. If you prefer, you can also reach me by email or connect with me on Reddit at Navigatetech.