basforge

Search titles, text and the “If it doesn’t work” cases.

    RU

    Without a subscription: the pve-no-subscription repository, both enterprise ones off

    A fresh Proxmox points at the enterprise repositories — its own and Ceph’s — and they open only to a host with a subscription key: apt update fails with 401 Unauthorized, and the host doesn’t get even security fixes. Turn off both enterprise repositories and turn on pve-no-subscription: the packages are the same, they just arrive there earlier.

    Since 9.0 Proxmox runs on Debian 13 and keeps repositories in the deb822 format: one .sources file per source, one field per line. After install, /etc/apt/sources.list.d/ holds:

    debian.sources           Debian 13: trixie, trixie-updates, trixie-security
    pve-enterprise.sources   Proxmox VE enterprise — needs a subscription key
    ceph.sources             Ceph, also enterprise — needs a subscription key

    Switch in the UI: node › Updates › Repositories, Disable on both enterprise lines, then Add › No-Subscription. Proxmox writes a new proxmox.sources file and adds Enabled: no to the disabled ones:

    # /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
    
    # /etc/apt/sources.list.d/pve-enterprise.sources
    Types: deb
    URIs: https://enterprise.proxmox.com/debian/pve
    Suites: trixie
    Components: pve-enterprise
    Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
    Enabled: no

    http for no-subscription isn’t a mistake: package authenticity is checked by the signature with the key from Signed-By, not by TLS.

    What you risk. A package reaches pve-no-subscription after internal testing, and enterprise even later, once no-subscription users have installed it. A bug that slipped past the tests hits us first. So update the host by hand and not on a Friday evening, and back up the guests before a big update. The third repository, pve-test, is for those who test packages before everyone else; don’t enable it on a host with guests you care about.

    Don’t set up automatic host updates through unattended-upgrades (unattended-upgrades) for Proxmox: an update changes the kernel, QEMU and cluster services, and afterwards someone needs to check that everything came back up.

    If it doesn’t work

    apt update: The repository … ceph-squid trixie InRelease is not signed or 401 from enterprise.proxmox.com/debian/ceph-squid

    Cause
    Only pve-enterprise was turned off, but the Ceph repository in ceph.sources points at enterprise too.
    Fix
    Node › Updates › Repositories — the line with ceph-squid and enterprise — Disable. If the host doesn’t use Ceph, don’t add no-subscription for it at all.

    After a file edit apt update complains: Malformed entry … in sources file

    Cause
    In the deb822 format a blank line separates entries. An Enabled: no line appended after the blank line at the end of the file became a separate entry without Types and URIs.
    Fix
    Put Enabled: no inside the entry, with no blank line before it. The Disable button in the UI writes the file itself and never makes this mistake.

    How to check

    apt update                     # Hit or Get lines from download.proxmox.com, no 401 or Err
    apt policy pve-manager         # Candidate comes from http://download.proxmox.com/debian/pve trixie/pve-no-subscription