Can't access GUI after upgrade

L

LeonKlop

New Member
Aug 8, 2025
10
0
1
Hi, I've just upgraded my Proxmox and now I can't access the GUI anymore. I get a connection refused message.
 
Check if pveproxy service is running :
Code: 
systemctl status pveproxy.service
This service is listening on port 8006, if you get a connection refused, it probably means that the service is not (correctly) running.
 
A number of issues with similar symptoms that were reported recently end up being incomplete/failed upgrades. Please take a look at a few recent threads for advice on how to force-reinstall the packages.

Other than that, outputs of the following commands may be helpful both to you and community to assist:
ip a
curl -k https://localhost:8006
curl -k htts://[lan_ip_of_pve]:8006
systemctl |grep pve
pveversion -v


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Hi, thanks for the replies:
first:
systemctl status pveproxy.service
× pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: ena>
Active: failed (Result: exit-code) since Fri 2025-08-08 05:23:42 CEST; 14h>
Process: 1219 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited>
Process: 1221 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EX>
CPU: 456ms

Aug 08 05:23:42 proxmox systemd[1]: pveproxy.service: Scheduled restart job, re>
Aug 08 05:23:42 proxmox systemd[1]: Stopped pveproxy.service - PVE API Proxy Se>
Aug 08 05:23:42 proxmox systemd[1]: pveproxy.service: Start request repeated to>
Aug 08 05:23:42 proxmox systemd[1]: pveproxy.service: Failed with result 'exit->
Aug 08 05:23:42 proxmox systemd[1]: Failed to start pveproxy.service - PVE API >
lines 1-12/12 (END)...skipping...
× 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-08 05:23:42 CEST; 14h ago
Process: 1219 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SU>
Process: 1221 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EXCEPTION)
CPU: 456ms


Aug 08 05:23:42 proxmox systemd[1]: pveproxy.service: Scheduled restart job, restart counter>
Aug 08 05:23:42 proxmox systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Aug 08 05:23:42 proxmox systemd[1]: pveproxy.service: Start request repeated too quickly.
Aug 08 05:23:42 proxmox systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Aug 08 05:23:42 proxmox systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
~
~
~
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp86s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 48:21:0b:57:cc:9d brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 90:09:df:08:47:6a brd ff:ff:ff:ff:ff:ff
altname wlp0s20f3
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 48:21:0b:57:cc:9d brd ff:ff:ff:ff:ff:ff
inet 10.10.10.100/25 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::4a21:bff:fe57:cc9d/64 scope link
valid_lft forever preferred_lft forever
5: vmbr0.24@vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 48:21:0b:57:cc:9d brd ff:ff:ff:ff:ff:ff
inet 10.10.10.130/25 scope global vmbr0.24
valid_lft forever preferred_lft forever
inet6 fe80::4a21:bff:fe57:cc9d/64 scope link
valid_lft forever preferred_lft forever

root@proxmox:~# curl -k https://localhost:8006
curl: (7) Failed to connect to localhost port 8006 after 0 ms: Couldn't connect to server
root@proxmox:~# curl -k htts://[lan_ip_of_pve]:8006
curl: (3) bad range in URL position 9:
htts://[lan_ip_of_pve]:8006

root@proxmox:~# systemctl |grep pve
pveversion -v
etc-pve.mount loaded active mounted /etc/pve
pve-cluster.service loaded active running The Proxmox VE cluster filesystem
pve-firewall-commit.service loaded active exited Commit Proxmox VE Firewall changes
pve-firewall.service loaded active running Proxmox VE firewall
● pve-guests.service loaded failed failed PVE guests
● pve-ha-crm.service loaded failed failed PVE Cluster HA Resource Manager Daemon
● pve-ha-lrm.service loaded failed failed PVE Local HA Resource Manager Daemon
pve-lxc-syscalld.service loaded active running Proxmox VE LXC Syscall Daemon
pve-query-machine-capabilities.service loaded active exited PVE Query Machine Capabilities
pve-sdn-commit.service loaded active exited Commit Proxmox VE SDN changes
pvebanner.service loaded active exited Proxmox VE Login Banner
● pvedaemon.service loaded failed failed PVE API Daemon
pvefw-logger.service loaded active running Proxmox VE firewall logger
pvenetcommit.service loaded active exited Commit Proxmox VE network changes
● 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
dev-pve-swap.swap loaded active active /dev/pve/swap
pve-storage.target loaded active active PVE Storage Target
pve-daily-update.timer loaded active waiting Daily PVE download activities
proxmox-ve: 8.4.0 (running kernel: 6.8.12-13-pve)
pve-manager: 8.4.9 (running version: 8.4.9/649acf70aab54798)
proxmox-kernel-helper: 8.1.4
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.9-pve1
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.4
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.7
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.3-1
proxmox-backup-file-restore: 3.4.3-1
proxmox-backup-restore-image: 0.7.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.4
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.13
pve-cluster: 8.0.10
pve-container: 5.3.0
pve-docs: 8.4.1
pve-edk2-firmware: 4.2025.02-4~bpo12+1
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.8-pve1
 
I honestly don't know
I installed it last year and was investigating the features.
Just trying to understand Linux and Proxmox
 
bbgeek17 said:
A number of issues with similar symptoms that were reported recently end up being incomplete/failed upgrades. Please take a look at a few recent threads for advice on how to force-reinstall the packages.

Other than that, outputs of the following commands may be helpful both to you and community to assist:
ip a
curl -k https://localhost:8006
curl -k htts://[lan_ip_of_pve]:8006
systemctl |grep pve
pveversion -v


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
I've seen the other posts, but they all concluded in reinstalling the complete proxmox environment. But I don't have a backup, so I would lose everything, including my VM's.
Or is there a way to migrate these from de cli?
 
Hi,
please share the system journal for the current boot journalctl -b > /tmp/boot.txt.
 
Code: 
Aug 08 05:23:36 proxmox networking[874]: error: /etc/network/interfaces.d/*.save: line1: error processing line '^X'
Aug 08 05:23:36 proxmox /usr/sbin/ifup[874]: error: /etc/network/interfaces.d/*.save: line1: error processing line '^X'
Aug 08 05:23:36 proxmox networking[874]: error: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_156_Aug-08-2025_05:23:36.396997 <<<

It seems there is an issue with your network file: the first line contains a forbidden ASCII character. It’s also unusual that the *.save file is still present.
 
Last edited:
hidigoudi said:
Code: 
Aug 08 05:23:36 proxmox networking[874]: error: /etc/network/interfaces.d/*.save: line1: error processing line '^X'
Aug 08 05:23:36 proxmox /usr/sbin/ifup[874]: error: /etc/network/interfaces.d/*.save: line1: error processing line '^X'
Aug 08 05:23:36 proxmox networking[874]: error: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_156_Aug-08-2025_05:23:36.396997 <<<

It seems there is an issue with your network file: the first line contains a forbidden ASCII character. It’s also unusual that the *.save file is still present.
Click to expand...
When I look at the /etc/network/interfaces.d/ I can see two files.
Weird, should I delete these?
 
LeonKlop said:
When I look at the /etc/network/interfaces.d/ I can see two files.
Weird, should I delete these?
Click to expand...
Probably not, never delete files, in the worst case move them from this folder so that ifupdown2 package can proceed completely without issue during boot step.

You should also check content of faulty files with :
Code: 
cat -A /etc/network/interfaces.d/*.save
 
Last edited:
hidigoudi said:
Probably not, never delete files, in the worst case move them from this folder so that ifupdown2 package can proceed completely without issue during boot step.

You should also check content of faulty files with :
Code: 
cat -A /etc/network/interfaces.d/*.save
Click to expand...
@proxmox:~# cat -A /etc/network/interfaces.d/*.save
^X$
$
$
$
 
Alright, I think I've downloaded the right repo (was a debian command, I'm running Ubuntu)
Did the, Apt update, Apt upgrade and apt full-upgrade and ran these commands with the following output
ip a
curl -k https://localhost:8006
curl -k htts://[lan_ip_of_pve]:8006
systemctl |grep pve
pveversion -v
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp86s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 48:21:0b:57:cc:9d brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 90:09:df:08:47:6a brd ff:ff:ff:ff:ff:ff
altname wlp0s20f3
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 48:21:0b:57:cc:9d brd ff:ff:ff:ff:ff:ff
inet 10.10.10.100/25 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::4a21:bff:fe57:cc9d/64 scope link
valid_lft forever preferred_lft forever
5: vmbr0.24@vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 48:21:0b:57:cc:9d brd ff:ff:ff:ff:ff:ff
inet 10.10.10.130/25 scope global vmbr0.24
valid_lft forever preferred_lft forever
inet6 fe80::4a21:bff:fe57:cc9d/64 scope link
valid_lft forever preferred_lft forever
curl: (7) Failed to connect to localhost port 8006 after 0 ms: Couldn't connect to server
curl: (3) bad range in URL position 9:
htts://[lan_ip_of_pve]:8006
^
etc-pve.mount loaded active mounted /etc/pve
pve-cluster.service loaded active running The Proxmox VE cluster filesystem
pve-firewall-commit.service loaded active exited Commit Proxmox VE Firewall changes
pve-firewall.service loaded active running Proxmox VE firewall
● pve-guests.service loaded failed failed PVE guests
● pve-ha-crm.service loaded failed failed PVE Cluster HA Resource Manager Daemon
● pve-ha-lrm.service loaded failed failed PVE Local HA Resource Manager Daemon
pve-lxc-syscalld.service loaded active running Proxmox VE LXC Syscall Daemon
pve-query-machine-capabilities.service loaded active exited PVE Query Machine Capabilities
pve-sdn-commit.service loaded active exited Commit Proxmox VE SDN changes
pvebanner.service loaded active exited Proxmox VE Login Banner
● pvedaemon.service loaded failed failed PVE API Daemon
pvefw-logger.service loaded active running Proxmox VE firewall logger
pvenetcommit.service loaded active exited Commit Proxmox VE network changes
● 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
dev-pve-swap.swap loaded active active /dev/pve/swap
pve-storage.target loaded active active PVE Storage Target
pve-daily-update.timer loaded active waiting Daily PVE download activities
proxmox-ve: 8.4.0 (running kernel: 6.8.12-13-pve)
pve-manager: 8.4.10 (running version: 8.4.10/293f4abc4b22fa08)
proxmox-kernel-helper: 8.1.4
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.9-pve1
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.4
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.7
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.4-1
proxmox-backup-file-restore: 3.4.4-1
proxmox-backup-restore-image: 0.7.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.4
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.13
pve-cluster: 8.0.10
pve-container: 5.3.0
pve-docs: 8.4.1
pve-edk2-firmware: 4.2025.02-4~bpo12+1
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.8-pve1

Rebooted the server, but no changes. Anyone else an idea on how to proceed?
 
Found the cause, my repositories where commented with #
So the upgrade didn't get the right perl version and that is why it didn't start again. Got my server running, thanks all
 
(was a debian command, I'm running Ubuntu)
Click to expand...
Why run PVE on Ubuntu? There is no technical reason to prefer Ubuntu over Debian for this purpose. PVE is a Debian based environment.
 
hidigoudi said:
Why run PVE on Ubuntu? There is no technical reason to prefer Ubuntu over Debian for this purpose. PVE is a Debian based environment.
Click to expand...
Maybe a little bit of a confusion, I'm running Ubuntu on my server
The little I know of Ubuntu, it's still more than Debian. So that's why
 
You must log in or register to reply here.
Top Bottom