How to Remove the Proxmox VE Subscription Warning

Every time you log into a fresh Proxmox VE installation, you are greeted with a popup: "You do not have a valid subscription for this server." While Proxmox VE is fully functional without a subscription, this message can be confusing — especially for homelabbers and small teams. This guide explains what the warning means, how to configure community repositories for updates, and when a subscription actually makes sense.

What the Subscription Warning Means

Proxmox VE is open-source software licensed under the AGPL. The subscription model funds development and provides access to the enterprise-grade repository, which contains thoroughly tested packages. Without a subscription, you can still use every feature — clustering, HA, ZFS, Ceph, and more. The popup is simply a reminder that enterprise support and the stable repo are available.

The warning appears once per login session and does not affect functionality in any way.

Proxmox Subscription Tiers

Proxmox offers four subscription levels, priced per CPU socket per year:

• Community — Basic access to the stable enterprise repository
• Basic — Enterprise repo plus business-hours support
• Standard — Faster response times and more support tickets
• Premium — Priority support with a dedicated account manager

For homelab and non-critical environments, the free community edition with the no-subscription repository is perfectly adequate.

Configuring the No-Subscription Repository

By default, Proxmox VE is configured to use the enterprise repository, which requires a subscription key. Without it, apt update will fail with a 401 error. You need to switch to the no-subscription repository.

# Disable the enterprise repository
mv /etc/apt/sources.list.d/pve-enterprise.list /etc/apt/sources.list.d/pve-enterprise.list.bak

# For Proxmox VE 8.x (Bookworm-based), add the no-subscription repo
echo "deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription" > /etc/apt/sources.list.d/pve-no-subscription.list

# For Ceph (if you use it), add the Ceph no-subscription repo
echo "deb http://download.proxmox.com/debian/ceph-reef bookworm no-subscription" > /etc/apt/sources.list.d/ceph.list

# Update package lists
apt update

Verify your base Debian repositories are also configured correctly in /etc/apt/sources.list:

# /etc/apt/sources.list should contain:
deb http://deb.debian.org/debian bookworm main contrib non-free-firmware
deb http://deb.debian.org/debian bookworm-updates main contrib non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free-firmware

Enterprise vs. Community Repository — What is the Difference?

The key difference is testing and release cadence:

• Enterprise repository (pve-enterprise) — Packages are held back and tested more extensively. Updates arrive less frequently but are considered production-safe. Requires a valid subscription key.
• No-subscription repository (pve-no-subscription) — Packages are released sooner. They are still stable, but have less testing than the enterprise channel. Suitable for homelabs, development, and non-critical workloads.
• Test repository (pvetest) — Bleeding-edge packages for developers. Not recommended for any production or homelab use.

Many administrators run the no-subscription repository for years without issues. The packages come from the same source — the difference is the additional QA layer applied to the enterprise channel.

Removing the Popup (Optional)

Some administrators choose to remove the subscription popup from the web interface. This involves modifying a JavaScript file and must be reapplied after every Proxmox update:

# Back up the original file first
cp /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js.bak

# Replace the subscription check
sed -Ei.bak "s/res === null \|\| res === undefined \|\| \!res || res.data.status.toLowerCase\(\) !== 'active'/false/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js

# Restart the web proxy to apply changes
systemctl restart pveproxy.service

Note that this modification is cosmetic only. It does not grant access to the enterprise repository, and it will be overwritten on package upgrades. You will need to reapply it after each apt upgrade that touches the widget toolkit.

Applying Updates Safely

Once your repositories are configured, keep your system updated:

# Update package lists and check for upgrades
apt update && apt list --upgradable

# Apply all available upgrades
apt dist-upgrade -y

# Check the current Proxmox VE version
pveversion -v

Always read the Proxmox VE release notes before applying major version upgrades. Minor updates within the same version are generally safe to apply without downtime, but kernel updates require a reboot.

Best Practices

• Consider subscribing if you run Proxmox in production — it directly funds the developers and ensures the project's future
• Snapshot before upgrading — Take a host-level ZFS snapshot or backup before applying updates
• Automate monitoring — Use tools like ProxmoxR to keep tabs on your nodes remotely, so you know immediately if an update causes issues
• Test updates on a non-critical node first if you run a cluster

Whether you subscribe or not, Proxmox VE remains one of the most capable open-source hypervisors available. Configure the right repository for your use case, keep your system updated, and the subscription popup is nothing more than a minor inconvenience.