Fixing Common Issues After Proxmox VE Upgrade

Web UI Shows Blank Page or JavaScript Errors

One of the most common issues after a Proxmox VE upgrade is the web interface showing a blank white page, loading indefinitely, or displaying JavaScript errors. This is almost always caused by cached assets in the browser conflicting with updated server-side files.

# First, restart the pveproxy service
systemctl restart pveproxy

# Check pveproxy is running and listening
systemctl status pveproxy
ss -tlnp | grep 8006

On the browser side, perform a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) and clear the browser cache. If the issue persists, try an incognito/private browsing window or a different browser entirely. In rare cases, you may need to clear the pveproxy cache on the server:

# Clear any compiled web UI assets
rm -rf /var/lib/pve-manager/
apt install --reinstall proxmox-widget-toolkit pve-manager

# Restart services
systemctl restart pvedaemon pveproxy

APT Source Mismatches and Repository Errors

After a major version upgrade, stale or incorrectly modified repository entries are a frequent source of problems. Symptoms include apt update failing with 404 errors, hash sum mismatches, or release file warnings.

# Check all configured repositories
cat /etc/apt/sources.list
ls -la /etc/apt/sources.list.d/
cat /etc/apt/sources.list.d/*.list

# Look for leftover old-release entries
grep -r "bullseye\|buster" /etc/apt/sources.list /etc/apt/sources.list.d/

All entries should reference the correct Debian codename for your Proxmox version (Bookworm for PVE 8, Trixie for PVE 9). Fix any mismatched entries:

# Example: fix a leftover bullseye entry in the enterprise repo
sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list.d/pve-enterprise.list

# If you have duplicate entries, remove the old file
rm /etc/apt/sources.list.d/pve-install-repo.list

# Clear apt cache and refresh
apt clean
apt update

If GPG key errors appear, import the correct Proxmox release key for your version:

# For PVE 8 (Bookworm)
wget https://enterprise.proxmox.com/debian/proxmox-release-bookworm.gpg \
  -O /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg

Network Interface Naming Changes

Major Debian upgrades can change network interface naming schemes. The transition from Bullseye to Bookworm, for instance, may rename interfaces if predictable naming rules are updated. If your node loses network connectivity after rebooting into the upgraded system, interface names may have shifted.

# Check current interface names
ip link show

# Compare with your network configuration
cat /etc/network/interfaces

# If interface names changed (e.g., eth0 became enp3s0), update the config
# Old:
#   auto eth0
#   iface eth0 inet static
# New:
#   auto enp3s0
#   iface enp3s0 inet static

# After editing, restart networking
systemctl restart networking

# Or apply without restart
ifreload -a

To prevent this in future upgrades, you can create a udev rule to pin interface names:

# Create persistent naming rule
cat > /etc/udev/rules.d/70-persistent-net.rules << 'EOF'
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"
EOF

Ceph Health Warnings After Upgrade

If you run Ceph, expect health warnings after a major Proxmox upgrade. Common warnings and their fixes:

# Check Ceph health details
ceph health detail

# HEALTH_WARN: mons are allowing insecure global_id reclaim
ceph config set mon auth_allow_insecure_global_id_reclaim false

# HEALTH_WARN: OSD count 0 < osd_pool_default_size 3
# This means OSDs haven't started yet - check their status
systemctl status ceph-osd.target
ceph osd tree

# HEALTH_WARN: noout flag(s) set
# If you set this during upgrade, unset it now
ceph osd unset noout

# HEALTH_WARN: DAEMON_OLD_VERSION - mixed versions detected
# Some daemons were not upgraded - check versions
ceph versions

If OSDs fail to start after the upgrade, check the logs and ensure the Ceph packages were fully upgraded:

# Check OSD logs
journalctl -u ceph-osd@0 --no-pager -n 50

# Reinstall Ceph packages
apt install --reinstall ceph-osd ceph-mon ceph-mgr

Container Template Issues

LXC containers may fail to start after a major upgrade due to incompatible AppArmor profiles, deprecated configuration options, or missing template dependencies.

# Check container configuration for deprecated options
cat /etc/pve/lxc/100.conf

# Common fix: update container to use newer features
pct set 100 --features nesting=1

# If AppArmor blocks the container
# Check logs
journalctl | grep -i apparmor | grep 100

# Temporarily disable AppArmor for the container to test
pct set 100 --apparmor unconfined
pct start 100

# Once confirmed working, set back to default
pct set 100 --apparmor default

Some older container templates may need updating. Download fresh templates from the Proxmox template repository:

# Update template list
pveam update

# List available templates
pveam available --section system

# Download a fresh template
pveam download local debian-12-standard_12.2-1_amd64.tar.zst

pveproxy Certificate Regeneration

If the web UI shows certificate errors after upgrading, the SSL certificate may need regeneration. This commonly happens when the hostname or IP address changed during the upgrade, or when the certificate files were corrupted.

# Check current certificate
openssl x509 -in /etc/pve/local/pve-ssl.pem -noout -text | head -15

# Regenerate the self-signed certificate
pvecm updatecerts --force

# Restart pveproxy to load the new certificate
systemctl restart pveproxy

# Verify the new certificate
openssl s_client -connect localhost:8006 < /dev/null 2>/dev/null | openssl x509 -noout -dates

General Post-Upgrade Health Check

Run through this checklist after every upgrade to catch issues early:

# Verify Proxmox version
pveversion -v

# Check all critical services
systemctl status pvedaemon pveproxy pvestatd pve-cluster corosync

# Verify storage is accessible
pvesm status

# Check for failed systemd units
systemctl --failed

# Review system logs for errors
journalctl -p err -b --no-pager | tail -30

Post-upgrade troubleshooting is much easier when you have baseline data to compare against. ProxmoxR maintains historical metrics for your Proxmox environment, making it straightforward to identify what changed and when issues began after an upgrade.