[SOLVED] No web interface after pve 9 upgrade!

A

alex01763

Member
Feb 28, 2023
32
3
13
Hello everyone,

I just did the upgrade from 8.4.11 to 9. I followed the official guide at https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 , and all was going well untill I rebooted the server. Just as the server booted up again it told me and is keep telling me, that it failed to start the following services:

Since this shows up on boot, I would like to show the picture of the monitor, but my monitor is too glossy and I can't take a picture without me being included. So this is the best I can give at the moment.
  • pvestatd.service
  • pvedaemon.service
  • pvedaemon.service
  • pveproxy.service
  • pvedaemon.service
For some reason it shows me the pvedaemon service three times, so I don't know what is going on there too. Anyways, after that when the server restarted I couldn't get it to show the web ui again. I can ssh into it just fine, and the server can ping external sources too. I think I figured out that pveproxy.service is in charge of handling the web ui, but when I systemctl status pveproxy.service, it says it failed, and I'm scared to break anything any further. Can anyone help me out here?
 
Check the status and logs of the failed services
Bash: 
systemctl --failed
systemctl status SERVICEHERE
journalctl -ru SERVICEHERE

alex01763 said:
my monitor is too glossy and I can't take a picture without me being included
Click to expand...
You could take pictures from an angle?
1755260121841.png
 
Last edited:
  • Like
Reactions: alex01763
Impact said:
Check the status and logs of the failed services
Bash: 
systemctl --failed
systemctl status SERVICEHERE
journalctl -ru SERVICEHERE
Click to expand...

systemctl -- failed:
Code: 
  UNIT                 LOAD   ACTIVE SUB    DESCRIPTION         
● pve-guests.service   loaded failed failed PVE guests
● pvedaemon.service    loaded failed failed PVE API Daemon
● pveproxy.service     loaded failed failed PVE API Proxy Server
● pvescheduler.service loaded failed failed Proxmox VE scheduler
● pvestatd.service     loaded failed failed PVE Status Daemon

status pve-guests.service
Code: 
× pve-guests.service - PVE guests
     Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Fri 2025-08-15 20:51:09 KST; 39min ago
    Process: 2790 ExecStartPre=/usr/share/pve-manager/helpers/pve-startall-delay (code=exited, status=0/SUCCESS)
    Process: 2963 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=17)
   Main PID: 2963 (code=exited, status=17)
        CPU: 694ms

Aug 15 20:51:09 node-main pvesh[2963]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 14.
Aug 15 20:51:09 node-main pvesh[2963]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 15.
Aug 15 20:51:09 node-main pvesh[2963]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 15.
Aug 15 20:51:09 node-main pvesh[2963]: Compilation failed in require at /usr/share/perl5/PVE/CLI/pvesh.pm line 16.
Aug 15 20:51:09 node-main pvesh[2963]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pvesh.pm line 16.
Aug 15 20:51:09 node-main pvesh[2963]: Compilation failed in require at /usr/bin/pvesh line 6.
Aug 15 20:51:09 node-main pvesh[2963]: BEGIN failed--compilation aborted at /usr/bin/pvesh line 6.
Aug 15 20:51:09 node-main systemd[1]: pve-guests.service: Main process exited, code=exited, status=17/n/a
Aug 15 20:51:09 node-main systemd[1]: pve-guests.service: Failed with result 'exit-code'.
Aug 15 20:51:09 node-main systemd[1]: Failed to start pve-guests.service - PVE guests.

pvedaemon:
Code: 
× pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Fri 2025-08-15 20:51:09 KST; 41min ago
    Process: 2958 ExecStart=/usr/bin/pvedaemon start (code=exited, status=17)
        CPU: 503ms

Aug 15 20:51:09 node-main systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
Aug 15 20:51:10 node-main systemd[1]: pvedaemon.service: Start request repeated too quickly.
Aug 15 20:51:10 node-main systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Aug 15 20:51:10 node-main systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
Aug 15 20:51:11 node-main systemd[1]: pvedaemon.service: Start request repeated too quickly.
Aug 15 20:51:11 node-main systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Aug 15 20:51:11 node-main systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
Aug 15 20:51:12 node-main systemd[1]: pvedaemon.service: Start request repeated too quickly.
Aug 15 20:51:12 node-main systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Aug 15 20:51:12 node-main systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.

pveproxy:
[CODE/
× pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2025-08-15 20:51:12 KST; 42min ago
Process: 3110 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 3121 ExecStart=/usr/bin/pveproxy start (code=exited, status=17)
CPU: 773ms

Aug 15 20:51:12 node-main systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Aug 15 20:51:12 node-main systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Aug 15 20:51:12 node-main systemd[1]: pveproxy.service: Start request repeated too quickly.
Aug 15 20:51:12 node-main systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Aug 15 20:51:12 node-main systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
[/CODE]

pvescheduler:
Code: 
× pvescheduler.service - Proxmox VE scheduler
     Loaded: loaded (/lib/systemd/system/pvescheduler.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Fri 2025-08-15 20:51:09 KST; 43min ago
    Process: 2980 ExecStart=/usr/bin/pvescheduler start (code=exited, status=255/EXCEPTION)
        CPU: 392ms

Aug 15 20:51:09 node-main pvescheduler[2980]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Jobs/VZDump.pm line 10, <DATA> line 960.
Aug 15 20:51:09 node-main pvescheduler[2980]: Compilation failed in require at /usr/share/perl5/PVE/Jobs.pm line 9, <DATA> line 960.
Aug 15 20:51:09 node-main pvescheduler[2980]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Jobs.pm line 9, <DATA> line 960.
Aug 15 20:51:09 node-main pvescheduler[2980]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvescheduler.pm line 8, <DATA> line 960.
Aug 15 20:51:09 node-main pvescheduler[2980]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvescheduler.pm line 8, <DATA> line >
Aug 15 20:51:09 node-main pvescheduler[2980]: Compilation failed in require at /usr/bin/pvescheduler line 6, <DATA> line 960.
Aug 15 20:51:09 node-main pvescheduler[2980]: BEGIN failed--compilation aborted at /usr/bin/pvescheduler line 6, <DATA> line 960.
Aug 15 20:51:09 node-main systemd[1]: pvescheduler.service: Control process exited, code=exited, status=255/EXCEPTION
Aug 15 20:51:09 node-main systemd[1]: pvescheduler.service: Failed with result 'exit-code'.
Aug 15 20:51:09 node-main systemd[1]: Failed to start pvescheduler.service - Proxmox VE scheduler.

pvestatd:
Code: 
× pvestatd.service - PVE Status Daemon
     Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Fri 2025-08-15 20:51:06 KST; 44min ago
    Process: 2039 ExecStart=/usr/bin/pvestatd start (code=exited, status=255/EXCEPTION)
        CPU: 527ms

Aug 15 20:51:06 node-main pvestatd[2039]: unknown file 'ha/rules.cfg' at /usr/share/perl5/PVE/Cluster.pm line 524.
Aug 15 20:51:06 node-main pvestatd[2039]: Compilation failed in require at /usr/share/perl5/PVE/QemuServer.pm line 36.
Aug 15 20:51:06 node-main pvestatd[2039]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuServer.pm line 36.
Aug 15 20:51:06 node-main pvestatd[2039]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvestatd.pm line 21.
Aug 15 20:51:06 node-main pvestatd[2039]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvestatd.pm line 21.
Aug 15 20:51:06 node-main pvestatd[2039]: Compilation failed in require at /usr/bin/pvestatd line 9.
Aug 15 20:51:06 node-main pvestatd[2039]: BEGIN failed--compilation aborted at /usr/bin/pvestatd line 9.
Aug 15 20:51:06 node-main systemd[1]: pvestatd.service: Control process exited, code=exited, status=255/EXCEPTION
Aug 15 20:51:06 node-main systemd[1]: pvestatd.service: Failed with result 'exit-code'.
Aug 15 20:51:06 node-main systemd[1]: Failed to start pvestatd.service - PVE Status Daemon.

journalctls are too long to include all of them in this post, but they are like
Code: 
Aug 15 20:51:06 node-main systemd[1]: Failed to start pvestatd.service - PVE Status Daemon.
Aug 15 20:51:06 node-main systemd[1]: pvestatd.service: Failed with result 'exit-code'.
Aug 15 20:51:06 node-main systemd[1]: pvestatd.service: Control process exited, code=exited, status=255/EXCEPTION
[/CODE/
with differrent exit codes.

[QUOTE="Impact, post: 792303, member: 161952"]

You could take pictures from an angle?
[/QUOTE]
 
That looks like a unfinished upgrade. Please check and share
Bash: 
apt update
apt dist-upgrade
apt install -f
And if that doesn't help you can try to reinstall the package(s)
Bash: 
apt install --reinstall pve-manager pve-cluster qemu-server
You can check which package provides a binary (see ExecStart) or file via something like dpkg -S /usr/bin/pvesh or dpkg -S /usr/share/perl5/PVE/Cluster.pm.
Please don't quote whole messages that are directly above yours.
 
Last edited:
  • Like
Reactions: alex01763
Impact said:
That looks like an unfinished upgrade. Please check and share
Bash: 
apt update
apt dist-upgrade
apt install -f
And if that doesn't help you can try to reinstall the package(s)
Bash: 
apt install --reinstall pve-manager pve-cluster qemu-server
You can check which package provides a binary (see ExecStart) or file via something like dpkg -S /usr/bin/pvesh or dpkg -S /usr/share/perl5/PVE/Cluster.pm.
Please don't quote whole messages that are directly above yours.
Click to expand...
Strange... there are 75 packages that can be upgraded when I run apt update, but none can actually be upgraded when I run apt upgrade or dist-upgrade.

when I run <span>apt</span> <span>install</span> --reinstall pve-manager pve-cluster qemu-server ,

Code: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libpve-rs-perl : Depends: perl (>= 5.40.1-6) but 5.36.0-7+deb12u2 is to be installed
                  Depends: perlapi-5.40.1 but it is not installable
                  Depends: libapt-pkg7.0 (>= 1.9~) but it is not installable
                  Depends: libc6 (>= 2.39) but 2.36-9+deb12u10 is to be installed
                  Depends: libssl3t64 (>= 3.0.0) but it is not installable
 proxmox-rrd-migration-tool : Depends: libc6 (>= 2.39) but 2.36-9+deb12u10 is to be installed
                              Depends: librrd8t64 (>= 1.5.3) but it is not going to be installed
 pve-cluster : Depends: perl (>= 5.40.1-6) but 5.36.0-7+deb12u2 is to be installed
               Depends: perlapi-5.40.1 but it is not installable
               Depends: libfuse2t64 (>= 2.9.2) but it is not installable
               Depends: libglib2.0-0t64 (>= 2.76.0) but it is not installable
               Depends: librrd8t64 (>= 1.4~rc2) but it is not going to be installed
 qemu-server : Depends: pve-firewall (>= 6.0.3) but 5.1.2 is to be installed
               Depends: libc6 (>= 2.38) but 2.36-9+deb12u10 is to be installed
               Depends: libglib2.0-0t64 (>= 2.12.0) but it is not installable
E: Unable to correct problems, you have held broken packages.

So I think something might have gone wrong during the upgrade, I just don't know what
 
Last edited:
alex01763 said:
If I run apt policy and don't see anything strange, i should be fine, right? At least I think that's what the documents said.
Click to expand...
Yeah I was wondering if you still had non-trixie stuff present causing conflicting package version requirements (if you had the ceph sources for example, or the file change had been reverted).
 
  • Like
Reactions: alex01763
richardnpaul said:
Yeah I was wondering if you still had non-trixie stuff present causing conflicting package version requirements (if you had the ceph sources for example, or the file change had been reverted).
Click to expand...
I just double checked the souce files and I think I should be good... I think...?
 
By the way, pve8to9 returns this error if this helps anything:
Code: 
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_ADDRESS = "LOCALE.UTF-8",
    LC_NAME = "LOCALE.UTF-8",
    LC_MONETARY = "LOCALE.UTF-8",
    LC_PAPER = "LOCALE.UTF-8",
    LC_IDENTIFICATION = "LOCALE.UTF-8",
    LC_TELEPHONE = "LOCALE.UTF-8",
    LC_MEASUREMENT = "LOCALE.UTF-8",
    LC_NUMERIC = "LOCALE.UTF-8",
    LANG = "LOCALE.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
Attempt to reload PVE/HA/Config.pm aborted.
Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20.
Compilation failed in require at /usr/share/perl5/PVE/API2/LXC/Status.pm line 24.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/LXC/Status.pm line 29.
Compilation failed in require at /usr/share/perl5/PVE/API2/LXC.pm line 28.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/LXC.pm line 28.
Compilation failed in require at /usr/share/perl5/PVE/CLI/pve8to9.pm line 10.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pve8to9.pm line 10.
Compilation failed in require at /usr/bin/pve8to9 line 6.
BEGIN failed--compilation aborted at /usr/bin/pve8to9 line 6.

LOCALE reveals where I live so I just replaced all of it
 
I took a deeper look into the logs after taking a nap. I think the problem lays here in the output of apt upgrade

Code: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  proxmox-kernel-6.5 proxmox-kernel-6.5.13-6-pve-signed proxmox-kernel-6.8.12-4-pve-signed proxmox-kernel-6.8.12-8-pve-signed
Use 'sudo apt autoremove' to remove them.
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 libnvpair3linux libproxmox-backup-qemu0 libproxmox-rs-perl
  libpve-network-api-perl libpve-network-perl libpve-rs-perl libpve-u2f-server-perl librados2 librados2-perl libradosstriper1 librbd1 librgw2
  librrds-perl libtpms0 libuutil3linux lvm2 lxc-pve lxcfs netdata netdata-plugin-apps netdata-plugin-debugfs netdata-plugin-ebpf
  netdata-plugin-network-viewer netdata-plugin-nfacct netdata-plugin-perf netdata-plugin-slabinfo netdata-plugin-systemd-journal
  proxmox-backup-client proxmox-backup-file-restore proxmox-firewall proxmox-mail-forward proxmox-mini-journalreader proxmox-termproxy proxmox-ve
  proxmox-websocket-tunnel pve-cluster pve-container pve-esxi-import-tools pve-firewall 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 vncterm zfs-initramfs zfs-zed zfsutils-linux
0 upgraded, 0 newly installed, 0 to remove and 75 not upgraded.

it says all the pve related stuff are kept back. Normally I would have just apt install -ed all of them manually, but is it safe to do that?
 
leesteken said:
Why are they kept back? What is the output of apt update and the output of grep -HR '' /etc/apt/sources.list*?
Click to expand...
I'm not sure but I think python and perl are having version problems. python is at 3.11 and not upgrading to 3.13 and perl is stuck at 5.36. I've been trying to build from source but had no luck

here's the output:

Code: 
/etc/apt/sources.list.d/pve-enterprise.list.dpkg-dist:deb https://enterprise.proxmox.com/debian/pve trixie pve-enterprise
/etc/apt/sources.list.d/netdata.sources:X-Repolib-Name: Netdata stable repository
/etc/apt/sources.list.d/netdata.sources:Types: deb
/etc/apt/sources.list.d/netdata.sources:URIs: http://repository.netdata.cloud/repos/stable/debian/
/etc/apt/sources.list.d/netdata.sources:Suites: trixie/
/etc/apt/sources.list.d/netdata.sources:Signed-By: /usr/share/keyrings/netdata-archive-keyring.gpg
/etc/apt/sources.list.d/netdata.sources:By-Hash: Yes
/etc/apt/sources.list.d/netdata.sources:Enabled: Yes
/etc/apt/sources.list.d/netdata.sources:X-Repolib-Name: Netdata repository configuration repository
/etc/apt/sources.list.d/netdata.sources:Types: deb
/etc/apt/sources.list.d/netdata.sources:URIs: http://repository.netdata.cloud/repos/repoconfig/debian/
/etc/apt/sources.list.d/netdata.sources:Suites: trixie/
/etc/apt/sources.list.d/netdata.sources:Signed-By: /usr/share/keyrings/netdata-archive-keyring.gpg
/etc/apt/sources.list.d/netdata.sources:By-Hash: Yes
/etc/apt/sources.list.d/netdata.sources:Enabled: Yes
/etc/apt/sources.list.d/proxmox.sources:Types: deb
/etc/apt/sources.list.d/proxmox.sources:URIs: http://download.proxmox.com/debian/pve
/etc/apt/sources.list.d/proxmox.sources:Suites: trixie
/etc/apt/sources.list.d/proxmox.sources:Components: pve-no-subscription
/etc/apt/sources.list.d/proxmox.sources:#Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
/etc/apt/sources.list.d/pve-enterprise.sources:#Types: deb
/etc/apt/sources.list.d/pve-enterprise.sources:#URIs: https://enterprise.proxmox.com/debian/pve
/etc/apt/sources.list.d/pve-enterprise.sources:#Suites: trixie
/etc/apt/sources.list.d/pve-enterprise.sources:#Components: pve-enterprise
/etc/apt/sources.list.d/pve-enterprise.sources:#Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
 
Last edited:
here's my result of apt policy:
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 Packages
release o=Proxmox,a=stable,n=trixie,l=Proxmox Debian Repository,c=pve-no-subscription,b=amd64
origin download.proxmox.com
500 http://repository.netdata.cloud/repos/repoconfig/debian trixie/ Packages
release v=13,o=Netdata,n=trixie,l=Netdata,c=
origin repository.netdata.cloud
500 http://repository.netdata.cloud/repos/stable/debian trixie/ Packages
release v=13,o=Netdata,n=trixie,l=Netdata,c=
origin repository.netdata.cloud
Pinned packages:

and for some reason I just found out that intel-microcode package is not available
 
  • Like
Reactions: alex01763 and leesteken
alex01763 said:
Code: 
/etc/apt/sources.list.d/pve-enterprise.list.dpkg-dist:deb https://enterprise.proxmox.com/debian/pve trixie pve-enterprise
/etc/apt/sources.list.d/netdata.sources:X-Repolib-Name: Netdata stable repository
/etc/apt/sources.list.d/netdata.sources:Types: deb
/etc/apt/sources.list.d/netdata.sources:URIs: http://repository.netdata.cloud/repos/stable/debian/
/etc/apt/sources.list.d/netdata.sources:Suites: trixie/
/etc/apt/sources.list.d/netdata.sources:Signed-By: /usr/share/keyrings/netdata-archive-keyring.gpg
/etc/apt/sources.list.d/netdata.sources:By-Hash: Yes
/etc/apt/sources.list.d/netdata.sources:Enabled: Yes
/etc/apt/sources.list.d/netdata.sources:X-Repolib-Name: Netdata repository configuration repository
/etc/apt/sources.list.d/netdata.sources:Types: deb
/etc/apt/sources.list.d/netdata.sources:URIs: http://repository.netdata.cloud/repos/repoconfig/debian/
/etc/apt/sources.list.d/netdata.sources:Suites: trixie/
/etc/apt/sources.list.d/netdata.sources:Signed-By: /usr/share/keyrings/netdata-archive-keyring.gpg
/etc/apt/sources.list.d/netdata.sources:By-Hash: Yes
/etc/apt/sources.list.d/netdata.sources:Enabled: Yes
/etc/apt/sources.list.d/proxmox.sources:Types: deb
/etc/apt/sources.list.d/proxmox.sources:URIs: http://download.proxmox.com/debian/pve
/etc/apt/sources.list.d/proxmox.sources:Suites: trixie
/etc/apt/sources.list.d/proxmox.sources:Components: pve-no-subscription
/etc/apt/sources.list.d/proxmox.sources:#Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
/etc/apt/sources.list.d/pve-enterprise.sources:#Types: deb
/etc/apt/sources.list.d/pve-enterprise.sources:#URIs: https://enterprise.proxmox.com/debian/pve
/etc/apt/sources.list.d/pve-enterprise.sources:#Suites: trixie
/etc/apt/sources.list.d/pve-enterprise.sources:#Components: pve-enterprise
/etc/apt/sources.list.d/pve-enterprise.sources:#Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
Click to expand...
You are missing the Debian repositories. That would hinder Promxox packages as they depend on Debian. You also have the no-subscription and the enterprise repository both enabled. Your also have other repositories enabled which may or may not interfere with Proxmox. This could have been discovered six hours ago.
Maybe disable those netdata repositories temporarily and chose between no-subscription and the enterprise repository for Proxmox.Definitely add the Debian repositories: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_debian_base_repositories before trying to install packages and update your system.

EDIT: When and why did you decide to remove the Debian repositories (which are mentioned in the upgrade guide your linked)?
 
Last edited:
  • Like
Reactions: alex01763 and UdoB
You must log in or register to reply here.
Top Bottom