Fixing Proxmox Update Errors A Step-by-Step Guide

Introduction

Proxmox Virtual Environment (Proxmox VE) is an open-source server virtualization platform that combines powerful virtualization technologies like KVM (Kernel-based Virtual Machine) for virtual machines and LXC (Linux Containers) for lightweight containerization. It is based on Debian Linux and provides a robust, enterprise-ready solution for managing virtual machines and containers within a single interface.

Why Use Proxmox?

1- Free & Open Source – Proxmox is free to use with a no-subscription option, making it an excellent choice for developers, IT professionals, and businesses looking for a cost-effective virtualization solution.
2- Web-Based Management – Proxmox provides a user-friendly web interface, eliminating the need for complex command-line interactions.
3- Cluster & High Availability – It supports clustering multiple Proxmox nodes and offers high availability (HA) for critical workloads.
4- Integrated Backup Solutions – With built-in backup and restore features, it ensures data safety with options like Proxmox Backup Server.
5- Networking & Storage Flexibility – Proxmox supports multiple storage types (ZFS, Ceph, LVM, NFS, etc.) and advanced networking capabilities. 6- Support for Multiple OS – You can run various operating systems, including Windows, Linux distributions, and BSD-based systems.

Who Should Use Proxmox?

Proxmox VE is ideal for system administrators, IT infrastructure teams, homelab enthusiasts, and enterprises looking for a reliable and scalable virtualization solution. Whether you’re running small test environments or large-scale data centers, Proxmox provides the flexibility and efficiency needed for modern virtualization.

The Problem: Facing the Proxmox Update Error

It was just another day managing my Proxmox server when I decided to update the system. I ran the usual update command:

apt update

Everything seemed normal at first, with repositories loading from Debian and Proxmox. But suddenly, an error message appeared:

Err:6 https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease
  401  Unauthorized [IP: 117.120.5.24 443]
E: Failed to fetch https://enterprise.proxmox.com/debian/ceph-quincy/dists/bookworm/InRelease  401  Unauthorized
E: The repository 'https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease' is not signed.

At this moment, I realized the issue: Proxmox was trying to access the Enterprise repository, which requires a paid subscription. Since I didn’t have a subscription, the repository was rejecting access, preventing my system from updating.

The Solution: Switching to the No-Subscription Repository

To resolve this, I followed these steps:

Step 1: Disable the Enterprise Repository

I needed to disable the Proxmox Enterprise repository to avoid further errors. To do this, I edited the repository file:

nano /etc/apt/sources.list.d/ceph.list

Inside the file, I found this line:

deb https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease

I simply commented it out by adding a # at the beginning of the line:

# deb https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease

Then, I saved the file (CTRL + X, then Y, and Enter). Alternatively, for a quick fix, I could have run this command:

echo "# deb https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease" > /etc/apt/sources.list.d/ceph.list

Step 2: Enable the No-Subscription Repository

Since I didn’t have a Proxmox subscription, I needed to use the No-Subscription repository instead. To ensure it was enabled, I ran:

echo "deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription" > /etc/apt/sources.list.d/pve-no-subscription.list

This command replaces any existing Proxmox repository configuration with the correct one for non-enterprise users.

Step 3: Update and Upgrade the System

Now that the correct repository was in place, I proceeded with updating the system:

apt update && apt dist-upgrade -y

This time, the update completed successfully without any authentication errors!

Step 4: (Optional) Remove the Enterprise Repository File

If I wanted to completely remove the enterprise repository file instead of just disabling it, I could run:

rm /etc/apt/sources.list.d/ceph.list

Conclusion: A Smooth Proxmox Update

By making these changes, I successfully bypassed the Proxmox Enterprise repository error and was able to keep my Proxmox system updated without a subscription. This method ensures that updates continue to work while avoiding unnecessary authentication issues. Now, my Proxmox server runs smoothly, and I can confidently manage updates without interruptions. If you ever face a similar issue, follow these steps and regain control of your Proxmox updates effortlessly!

Feedback and Questions

Your insights drive us! For any questions, feedback, or thoughts, feel free to connect:

1. Email: shady@shadynagy.com
2. Twitter: @ShadyNagy_
3. LinkedIn: Shady Nagy
4. GitHub: ShadyNagy

If you found this guide beneficial, don’t hesitate to share it with your network. Until the next guide, happy coding! 🚀