[SOLVED] Stuck on 8.4.16 after trying to upgrade to 9.x

fleet-command

New Member
Feb 17, 2026
2
1
3
After upgrading to proxmox 9 and running pve8to9 and everything looking ok, I restarted the machine and noticed that couldn't load the proxmox interface.

The browser console reported:

Code:
Status 500 no such file '/PVE/StdWorkspace.js'

Then running pveversion -v I can see that I'm still stuck in proxmox 8.4.0

Bash:
proxmox-ve: 8.4.0 (running kernel: 6.5.13-1-pve)
pve-manager: 8.4.16 (running version: 8.4.16/368e3c45c15b895c)
proxmox-kernel-helper: 9.0.4
pve-kernel-5.11: 7.0-10
proxmox-kernel-6.17.9-1-pve-signed: 6.17.9-1
proxmox-kernel-6.17: 6.17.9-1
proxmox-kernel-6.8: 6.8.12-18
proxmox-kernel-6.8.12-18-pve-signed: 6.8.12-18
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
...

Then running dist-upgrade I get that some packages have been kept back:

Bash:
apt-get dist-upgrade
The following packages have been kept back:
  apparmor ceph-common ceph-fuse corosync dmeventd dmsetup grub-common grub-efi-amd64-bin grub-pc-bin grub2-common libapparmor1 libcephfs2 libcrypt-openssl-rsa-perl libdevmapper-event1.02.1
  libdevmapper1.02.1 liblvm2cmd2.03 libnss-systemd libnvpair3linux libpam-systemd libproxmox-backup-qemu0 libproxmox-rs-perl libpve-http-server-perl libpve-network-api-perl libpve-network-perl
  libpve-rs-perl libpve-u2f-server-perl librados2 librados2-perl libradosstriper1 librbd1 librgw2 librrds-perl libsystemd-shared libsystemd0 libtpms0 libudev1 libuutil3linux lvm2 lxc-pve lxcfs
  proxmox-backup-client proxmox-backup-file-restore proxmox-firewall proxmox-mail-forward proxmox-mini-journalreader proxmox-offline-mirror-helper proxmox-termproxy proxmox-ve proxmox-websocket-tunnel
  pve-cluster pve-container pve-esxi-import-tools pve-firewall pve-ha-manager pve-lxc-syscalld pve-manager pve-qemu-kvm python3-ceph-argparse python3-ceph-common python3-cephfs python3-rados
  python3-rbd python3-rgw qemu-server rrdcached smartmontools spiceterm swtpm swtpm-libs swtpm-tools systemd systemd-sysv udev vncterm zfs-initramfs zfs-zed zfsutils-linux
0 upgraded, 0 newly installed, 0 to remove and 77 not upgraded.

The has /etc/apt/sources.list been disabled and using just the new deb822 format

Code:
cat /etc/apt/sources.list
# Keep the .sources file and remove the entry from sources.list
# This aligns with how modern Debian and Proxmox expect repositories to be configured.
# cat /etc/apt/sources.list.d/proxmox.sources

# deb http://ftp.debian.org/debian trixie main contrib non-free-firmware
# deb http://ftp.debian.org/debian trixie-updates main contrib non-free-firmware

# deb http://security.debian.org/debian-security trixie-security main contrib non-free-firmware

# deb http://download.proxmox.com/debian/pve trixie pve-no-subscription


# deb http://download.proxmox.com/debian/pve trixie pvetest

The /etc/apt/sources.list.d/proxmox.sources sources file

Code:
cat /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

Thanks in advance!
 
Found the issue, during my upgrade I mistakenly thought that I had migrated the Debian base repositories to the new format but no, ended just commenting them out :/

When I re-enabled the repositories in /etc/apt/sources.list and run apt update and apt dist-upgrade the problem was solved.
 
  • Like
Reactions: UdoB