thumb

If you’ve been using Proxmox, either the Virtual Environment (PVE) or the Backup Server (PBS), and you don’t have a valid subscription, you’ll consistently encounter a particular error message when attempting a system update using sudo apt update. This error usually points its fingers at the https://enterprise.proxmox.com repository. Fret not! This guide aims to help you understand this message and provide a way to work around it, especially if you’re using Proxmox without a subscription.

The Underlying Message

Ever tried running sudo apt update and been greeted with the following?

$ sudo apt update
Err: https://enterprise.proxmox.com/debian/pbs bookworm InRelease
  401  Unauthorized [IP: xx.xx.xx.xx 443]
E: The repository 'https://enterprise.proxmox.com/debian/pbs bookworm InRelease' is not signed.

So, What’s Going On?

The root of this issue lies in the fact that the enterprise.proxmox.com repository is a reserved space for Proxmox’s esteemed subscription holders. If you’re either not on their subscription list or there’s a hiccup in your subscription details, this error will be your unwanted guest.

This isn’t so much an ‘error’ in the typical sense but more of a notification from Proxmox developers. It indicates that there’s something amiss with your subscription.

Let’s Sort This Out

Note: Commands in this article are shown with sudo. If you’re logged into Proxmox (PVE or PBS) as root, simply omit the sudo prefix when executing commands.

Note: Throughout this guide, we’ve used bookworm as an example of a Debian release name. Depending on your Proxmox VE (PVE) or Proxmox Backup Server (PBS) version, you might be using a different Debian release name such as buster or bullseye. It’s crucial to replace bookworm with the correct release name for your setup.

To find out your release name, you can use the following command:

lsb_release -cs

This will display the codename of the Debian release your Proxmox installation is based on. Make sure to use this codename in place of bookworm when editing repository configurations.

Before we dive into tweaking configurations, it’s always a good idea to create a backup. You know, just in case.

For Proxmox Virtual Environment (PVE):

sudo cp /etc/apt/sources.list.d/pve-enterprise.list /etc/apt/sources.list.d/pve-enterprise.list.backup

For Proxmox Backup Server (PBS):

sudo cp /etc/apt/sources.list.d/pbs-enterprise.list /etc/apt/sources.list.d/pbs-enterprise.list.backup

For Proxmox Virtual Environment (PVE):

Let’s pop open the PVE enterprise repository configuration:

sudo nano /etc/apt/sources.list.d/pve-enterprise.list

Here, comment out the enterprise repository line, like so:

# deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise

Then, add the no-subscription repository for PVE, like so:

# PVE pve-no-subscription repository provided by proxmox.com,
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

Note: In the code block above, we’ve used “bookworm” as the Debian release name. If your system’s release name differs from “bookworm”, be sure to replace it with your specific release name in the provided code.

For Proxmox Backup Server (PBS):

Let’s pop open the PBS enterprise repository configuration:

sudo nano /etc/apt/sources.list.d/pbs-enterprise.list

Here, comment out the enterprise repository line for PBS, like so:

# deb https://enterprise.proxmox.com/debian/pbs bookworm pbs-enterprise

And add the no-subscription repository for PBS:

# PVE pve-no-subscription repository provided by proxmox.com,
deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription

Note: In the code block above, we’ve used “bookworm” as the Debian release name. If your system’s release name differs from “bookworm”, be sure to replace it with your specific release name in the provided code.

Once done, save your changes and make a graceful exit from the editor.

Refresh the repository cache:

sudo apt update

Now, you should be able to update your system without any errors.

Conclusion

Both Proxmox VE and Proxmox Backup Server are powerful tools in the realm of virtualization and backup solutions. While they function seamlessly with a valid subscription, users without one will regularly see the aforementioned message. Remember, this isn’t a bug or an unforeseen error; it’s a deliberate notification about the subscription status. With the steps provided in this guide, you can navigate around this message. But, as always, remember to backup before making system changes.

If this guide proved useful or if you have any additional insights, feel free to share your thoughts below. Until next time, happy virtualizing and backing up!