[SOLVED] - Can't seem to upgrade...

S

SkippyTheMagnificent

New Member
Jan 13, 2026
5
0
1
I am in the process of migrating FROM XCP-NG to Proxmox. I have 2 servers that I've already migrated (and one more to do after these two are working and clustered).
1 server is an Ryzen 9 host and it shows as Proxmox VE version 9.0.3 (I installed this one via an iPxe Proxmox image).
The other server (I couldn't get it to boot from PXE, so I went with the live ISO image, is a Xeon D host and it shows as version 9.1.1
I have verified, on both servers, that the debian.sources file already contains trixie sources and I've
Code: 
apt update && apt dist-upgrade
on both hosts to try and get them in sync (version-wise) with each other.
The 9.0.3 server still shows 9.0.3 after a reboot and
Code: 
root@pvetest:/etc/apt# pveversion
pve-manager/9.0.3/025864202ebb6109 (running kernel: 6.14.8-2-pve
And the 9.1.1 server shows
Code: 
root@pve:~# pveversion
pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve)

I'm trying to get these two servers in sync before I set up a cluster since all the docs I've found indicate that they should all be on the save version and patch number, and I've not started on the 3rd physical box, yet, since I wanted to get 2 of them up and running to give a little more room to migrate VMs over before I blasted away the last XCP-NG server.

I've tried doing all combinations of apt upgrade, apt dist-upgrade, apt full-upgrade, that I'm aware of, yet both of these hosts don't show any indication of being upgraded to the same version.

If it helps identify anything, here are the pveversion -v outputs from both hosts:
9.1.1 versioned host:
Code: 
root@pve:~# pveversion -v
proxmox-ve: 9.1.0 (running kernel: 6.17.2-1-pve)
pve-manager: 9.1.1 (running version: 9.1.1/42db4a6cf33dac83)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
proxmox-kernel-6.17: 6.17.2-1
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx11
intel-microcode: 3.20251111.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.4
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.0.15
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.3
libpve-rs-perl: 0.11.3
libpve-storage-perl: 9.0.18
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-3
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.20-1
proxmox-backup-file-restore: 4.0.20-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.2
pve-cluster: 9.0.7
pve-container: 6.0.18
pve-docs: 9.1.0
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.17-2
pve-ha-manager: 5.0.8
pve-i18n: 3.6.2
pve-qemu-kvm: 10.1.2-3
pve-xtermjs: 5.5.0-3
qemu-server: 9.0.30
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
...and the 9.0.3 versioned host:
Code: 
root@pvetest:/etc/apt# pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve)
pve-manager: 9.0.3 (running version: 9.0.3/025864202ebb6109)
proxmox-kernel-helper: 9.0.3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.14: 6.14.8-2
amd64-microcode: 3.20250311.1
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.3
libpve-network-perl: 1.1.6
libpve-rs-perl: 0.10.7
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2
lxc-pve: 6.0.4-2
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.9-1
proxmox-backup-file-restore: 4.0.9-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.1
proxmox-kernel-helper: 9.0.3
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.0
proxmox-widget-toolkit: 5.0.4
pve-cluster: 9.0.6
pve-container: 6.0.9
pve-docs: 9.0.7
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-3
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.16
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.3-pve1

Adding to the confusion, both hosts have identical /etc/apt/sources.list.d/debian.sources file contents, nothing in preferences.d, nothing in listchanges.conf or listchanges.conf.d... they are pretty much identical to each other.

Oh, and I do NOT have access to the enterprise repos since I'm a FOSS user.

Any help here would be GREATLY appreciated, so, Thank you in Advance!
 
Last edited:
leesteken said:
What is the actual output of apt update? There is probably a repository missing or incorrect or a DNS-problem.
Click to expand...
With the enterprise repository enabled, I get this on BOTH hosts:
Code: 
root@pve:~# apt update
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://security.debian.org/debian-security trixie-security InRelease
Err:4 https://enterprise.proxmox.com/debian/pve trixie InRelease
  401  Unauthorized [IP: 170.130.165.90 443]
Error: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/trixie/InRelease  401  Unauthorized [IP: 170.130.165.90 443]
Error: The repository 'https://enterprise.proxmox.com/debian/pve trixie InRelease' is not signed.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
If I disable the enterprise repo via the GUI or add
Code: 
Enabled: false
to the pve-enterprise.sources file, I get a clean apt update, like this:
Code: 
root@pvetest:~# apt update
Hit:1 http://deb.debian.org/debian trixie InRelease
Get:2 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB]
Get:3 http://security.debian.org/debian-security trixie-security InRelease [43.4 kB]
Fetched 90.7 kB in 0s (1,963 kB/s)
All packages are up to date.
 
SkippyTheMagnificent said:
But doesn't access to the enterprise repo require a subscription?
Click to expand...
Yes but the enterprise repository is slightly behind the latest updates which it gets in batches. All features and fixes are available for free (with source code) on the no-subscription repository (immediately as soon as they are pushed there from the test repository, which you can also use for free if you want).

EDIT: Any chance you can show the output as requested to try and help you with the issue you have?
EDIT2: It looks like the post with the output was caught in the spamfilter until a minute ago and I did not see it before.
 
Last edited:
  • Like
Reactions: Johannes S
leesteken said:
Yes but the enterprise repository is slightly behind the latest updates which it gets in batches. All features and fixes are available for free (with source code) on the no-subscription repository (immediately as soon as they are pushed there from the test repository, which you can also use for free if you want).

EDIT: Any chance you can show the output as requested to try and help you with the issue you have?
Click to expand...
I literally JUST (between the time I replied and your reply came back) stumbled across the no-subscription repo in the docs and added it; doing an update now to see if that gets the two servers in sync.
 
SkippyTheMagnificent said:
Solved. That's good to know, and it also fixes that annoying popup on startup about not having an enterprise license! Thank you both!
Click to expand...
Enjoy PVE and see you in a few weeks when you come back with "my GUI stopped working and I did not change anything".

This is based on the fact that you:
- informed us that you are not an Enterprise subscription user in the now deleted post
- enabled the no-sub repository to solve your update issue
- informed us that the "reminder" is now gone
- implying that you used one of the "helpful" scripts to modify the PVE code to suppress the reminder
- it would only be properly removed if you used Enterprise repo.
- these scripts are known to break PVE functionality between upgrades

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: Johannes S
You must log in or register to reply here.
Top Bottom