Proxmox unable to access Web Gui

sandihex

New Member
Oct 24, 2023
1
0
1
I've problem when access the Proxmox web gui after several upgrade, the problem seems from pveproxy, when I tried to access localhost:8006 using curl

root@labdata:~# curl -k https://localhost:8006 curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8006

and from the syslog I have

Oct 24 08:00:21 labdata pveproxy[15045]: Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1753. Oct 24 08:00:21 labdata pveproxy[20805]: failed to accept connection: Bad file descriptor Oct 24 08:00:21 labdata pveproxy[20805]: Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1753. Oct 24 08:00:21 labdata pveproxy[15207]: failed to accept connection: Bad file descriptor Oct 24 08:00:21 labdata pveproxy[15043]: worker 15207 finished

my promxom version engin

root@labdata:/etc/ssl/certs# pveversion pve-manager/7.3-3/c3928077 (running kernel: 5.15.74-1-pve) root@labdata:/etc/ssl/certs# pveversion -v proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve) pve-manager: 7.3-3 (running version: 7.3-3/c3928077) pve-kernel-5.15: 7.2-14 pve-kernel-helper: 7.2-14 pve-kernel-5.15.74-1-pve: 5.15.74-1 ceph-fuse: 15.2.17-pve1 corosync: 3.1.7-pve1 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.24-pve2 libproxmox-acme-perl: 1.4.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.2-5 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.2-8 libpve-guest-common-perl: 4.2-3 libpve-http-server-perl: 4.1-5 libpve-storage-perl: 7.2-12 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 5.0.0-3 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 proxmox-backup-client: 2.2.7-1 proxmox-backup-file-restore: 2.2.7-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.5.3 pve-cluster: 7.3-1 pve-container: 4.4-2 pve-docs: 7.3-1 pve-edk2-firmware: 3.20220526-1 pve-firewall: 4.2-7 pve-firmware: 3.5-6 pve-ha-manager: 3.5.1 pve-i18n: 2.8-1 pve-qemu-kvm: 7.1.0-4 pve-xtermjs: 4.16.0-1 qemu-server: 7.3-1 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.8.0~bpo11+2 vncterm: 1.7-1 zfsutils-linux: 2.1.6-pve1
 
Hi,

Have you tried to update the certificates using `pvecm updatecerts --force` command and then restart the pveproxy pvedaemon services using the following command:
Code:
systemctl restart pveproxy pvedaemon

pve-manager/7.3-3/c3928077 (running kernel: 5.15.74-1-pve)
Note that the Proxmox VE 5.x is already EOL [0], I recommend you to upgrade to the latest available version of Proxmox VE.

[0] https://pve.proxmox.com/pve-docs/chapter-pve-faq.html
 
`pvecm updatecerts --force`

Code:
systemctl restart pveproxy pvedaemon
I tried your commands but still have that problem:

Code:
curl -k https://localhost:8006
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to localhost:8006

but different proxmox version.

pveversion
Code:
pve-manager/8.1.3/b46aac3b42da5d15 (running kernel: 6.5.11-7-pve)

@sandihex
From my pveproxy log i can see that the proxy reponded with 403.

Now i remembered that I edited /etc/default/pveproxy to allow access from another subnet ip address but with that change I restricted access for localhost.
When I remove or allow the specific settings in that file. The curl works again.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!