Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bookworm/InRelease 401 Unauthorized [IP: 144.217.225.162 443]

[andersostling56]

Never run apt upgrade as it may not update everything, always use the procedure documented in the manual.

What procedure would that be? I found one section "System software" that recommended the normal apt update/upgrade process.
Another section talks about the non-subscription repo. I added that one and got this where the updates above is included but also proxmox specific packages. Is this method better?

The following NEW packages will be installed:
proxmox-default-kernel proxmox-kernel-6.2 proxmox-kernel-6.2.16-10-pve
The following packages will be upgraded:
base-files bind9-dnsutils bind9-host bind9-libs curl dbus dbus-bin dbus-daemon dbus-session-bus-common
dbus-system-bus-common ifupdown2 libc-bin libc-l10n libc6 libcurl3-gnutls libcurl4 libdbus-1-3
libgstreamer-plugins-base1.0-0 libjs-extjs libldb2 libnftables1 libnss-systemd libpam-systemd
libproxmox-rs-perl libpve-access-control libpve-cluster-api-perl libpve-cluster-perl libpve-common-perl
libpve-guest-common-perl libpve-http-server-perl libpve-rs-perl libpve-storage-perl librados2-perl
libsmbclient libsystemd-shared libsystemd0 libudev1 libwbclient0 libxml2 locales nftables postfix
proxmox-backup-client proxmox-backup-file-restore proxmox-kernel-helper proxmox-mail-forward proxmox-ve
proxmox-widget-toolkit pve-cluster pve-container pve-docs pve-firewall pve-i18n pve-kernel-6.2 pve-manager
pve-qemu-kvm samba-common samba-libs smbclient systemd systemd-boot systemd-boot-efi systemd-sysv udev
64 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 186 MB of archives.
After this operation, 582 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

 

[t.lamprecht]

Is it unwise to comment away the enterprise and ceph repos and do manual updates?

It's unwise to comment those out and not add a Proxmox VE repo one has access to.

I.e., you always need both:

• The base Debian repository set
• Exactly one repo from Proxmox VE, be it enterprise, pve-no-subscription or pvetest

As otherwise you won't get updates for core packages like kernel or QEMU and our software stack.

Note that Proxmox projects are also rolling releases, the point releases are merely snapshots so that we have a relatively up-to-date ISO installer, as it's easier to see if users use outdated software and as some admins need such releases to argue being able to update their infra to upper management.
And yes, while such point release snapshots get a bit more QA and target polishing when assembling them, all Proxmox projects are intended to be updated frequently.

 

[leesteken]

What procedure would that be? I found one section "System software" that recommended the normal apt update/upgrade process.

It states apt dist-upgrade, which is different from apt upgrade. I did not answer you original/actual question but I just wanted to warn you about apt upgrade as there are enough threads on this forum already of people running into problems.

Another section talks about the non-subscription repo. I added that one and got this where the updates above is included but also proxmox specific packages. Is this method better?

The no-subscription repository gets update earlier (and the test repository even earlier) than the enterprise repository, that's why the differ. Which one you find better depends on your use-case.

 

[t.lamprecht]

What procedure would that be? I found one section "System software" that recommended the normal apt update/upgrade process.

No it doesn't, it documents dist-upgrade, which is the safe command for Proxmox projects, the upgrade command you referred to can cause trouble as it refuses to remove existing packages – which is sometimes needed for a transition.

 

[andersostling56]

It's unwise to comment those out and not add a Proxmox VE repo one has access to.

I.e., you always need both:

• The base Debian repository set
• Exactly one repo from Proxmox VE, be it enterprise, pve-no-subscription or pvetest

As otherwise you won't get updates for core packages like kernel or QEMU and our software stack.

Note that Proxmox projects are also rolling releases, the point releases are merely snapshots so that we have a relatively up-to-date ISO installer, as it's easier to see if users use outdated software and as some admins need such releases to argue being able to update their infra to upper management.
And yes, while such point release snapshots get a bit more QA and target polishing when assembling them, all Proxmox projects are intended to be updated frequently.

Thank you Thomas. So I will stay on my pve-nonsubscription since it's "only" my homelab that is using Proxmox. It's indeed a fantastic piece of software! I have been using KVM/QEMU/virt-manager/XCP-NG for many years, but PVE has gone under my radar (until now). So far I have migrated or recreated a number of containers, vm's and configured NAS and backup. So simple and straightforward compared to other solutions!

 

[andersostling56]

No it doesn't, it documents dist-upgrade, which is the safe command for Proxmox projects, the upgrade command you referred to can cause trouble.

I stand corrected

 

[brandon-c]

After updating to 8.0.3 I am getting this error message when I run the updates

starting apt-get update
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://ftp.debian.org/debian bookworm InRelease
Hit:3 http://ftp.debian.org/debian bookworm-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bookworm InRelease
401 Unauthorized [IP: 144.217.225.162 443]
Hit:5 http://download.proxmox.com/debian/pve bookworm InRelease
Hit:6 http://download.proxmox.com/debian/ceph-quincy bookworm InRelease
Reading package lists...
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bookworm/InRelease 401 Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bookworm InRelease' is not signed.
TASK ERROR: command 'apt-get update' failed: exit code 100

I'm assuming you had the issue resolved not sure if it was mentioned above but the following resolved my issue that was the same

rm /etc/apt/sources.list.d/pve-enterprise.list

 

[droid4jeff]

I'm assuming you had the issue resolved not sure if it was mentioned above but the following resolved my issue that was the same

rm /etc/apt/sources.list.d/pve-enterprise.list

Sorry, didn't work for me.

 

[Bepp]

ls pve-enterprise.list pve-enterprise.list.dpkg-dist

That did the trick for me, thank you!

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

Content (To save you a google search if you face the same problem):

#deb https://enterprise.proxmox.com/debian/ceph-quincy bookworm enterprise
deb http://download.proxmox.com/debian/ceph-quincy bookworm no-subscription