[SOLVED] Unable to connect to web gui

J

Jaif

New Member
Sep 15, 2023
5
0
1
I've installed proxmox on a machine and I'm unable to connect to the web gui. I think I have the networking ironed-out, but I'm not clear where to go from there. Details:

- I reserved the IP I used in my router, and can see it attached. (Will do a range later)
- I can ssh to my proxmox machine with putty (logged in now)
- I can ping 8.8.8.8 from my machine, so it can get out to the internet.

When I try to get to the gui, it just hangs and eventually times-out. I've used windows/chrome, ipad/safari, and linux/firefox ... all timeout.

using https://192.168.1.50:8006/

(in case you want to make sure the syntax is right)
 
Hello

Lets try to get a little bit more information. Enter journalctl -f via ssh, then try to reach the web GUI.

If you manage to you could also post the output of journalctl -b here so we can see if there were any problems since boot.
 
When I ran -f , I see this repeated over and over:

Sep 15 08:28:56 proxmox1 pveproxy[867]: starting 2 worker(s)
Sep 15 08:28:56 proxmox1 pveproxy[867]: worker 15917 started
Sep 15 08:28:56 proxmox1 pveproxy[867]: worker 15918 started
Sep 15 08:28:56 proxmox1 pveproxy[15917]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2009.
Sep 15 08:28:56 proxmox1 pveproxy[15918]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2009.
Sep 15 08:29:01 proxmox1 cron[819]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Sep 15 08:29:01 proxmox1 pveproxy[15916]: worker exit
Sep 15 08:29:01 proxmox1 pveproxy[867]: worker 15916 finished
Sep 15 08:29:01 proxmox1 pveproxy[867]: starting 1 worker(s)
Sep 15 08:29:01 proxmox1 pveproxy[867]: worker 15921 started
Sep 15 08:29:01 proxmox1 pveproxy[15921]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2009.
Sep 15 08:29:01 proxmox1 pveproxy[15918]: worker exit
Sep 15 08:29:01 proxmox1 pveproxy[15917]: worker exit
Sep 15 08:29:01 proxmox1 pveproxy[867]: worker 15918 finished
Sep 15 08:29:01 proxmox1 pveproxy[867]: worker 15917 finished

The bolded part only happened once, I just included it here for completeness.

The output from -b is very long. I'll try to cut and paste some bits:

Sep 15 07:00:20 proxmox1 kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.16-3-pve root=/dev/mapper/pve-root>
Sep 15 07:00:20 proxmox1 kernel: Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-6.2.16-3-pve", will>
Sep 15 07:00:20 proxmox1 kernel: random: crng init done
S

Sep 15 07:00:20 proxmox1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS01], AE_NOT_F>
Sep 15 07:00:20 proxmox1 kernel: fbcon: Taking over console
Sep 15 07:00:20 proxmox1 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)
Sep 15 07:00:20 proxmox1 kernel: ACPI: Skipping parse of AML opcode: Scope (0x0010)
Sep 15 07:00:20 proxmox1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS02], AE_NOT_F>
Sep 15 07:00:20 proxmox1 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)

Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Sep 15 07:00:20 proxmox1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8

Sep 15 07:00:20 proxmox1 kernel: nvme nvme0: missing or invalid SUBNQN field.

Sep 15 07:00:20 proxmox1 kernel: Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0040-1050.sfi (-2)
Sep 15 07:00:20 proxmox1 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-56)

Sep 15 07:00:20 proxmox1 kernel: iwlwifi: No config found for PCI dev 54f0/0244, rev=0x370, rfid=0x10c000
Sep 15 07:00:20 proxmox1 kernel: iwlwifi: probe of 0000:00:14.3 failed with error -22
Sep 15 07:00:20 proxmox1 kernel: ZFS: Loaded module v2.1.12-pve1, ZFS pool version 5000, ZFS filesystem version 5

Sep 15 07:00:21 proxmox1 smartd[510]: Device: /dev/nvme0, number of Error Log entries increased from 41 to 42

Sep 15 07:00:26 proxmox1 systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Sep 15 07:00:26 proxmox1 pveproxy[868]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2009.
Sep 15 07:00:26 proxmox1 pveproxy[869]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2009.
Sep 15 07:00:26 proxmox1 pveproxy[870]: /etc/pve/local/pve-ssl.pem: failed to use local certificate chain (cert_file or cert) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 2009.
Sep 15 07:00:26 proxmox1 systemd[1]: Starting pve-ha-lrm.service - PVE Local HA Resource Manager Daemon...
Sep 15 07:00:26 proxmox1 systemd[1]: Starting spiceproxy.service - PVE SPICE Proxy Server...
 
First of all: there are a lot of posts suggesting hardware compatibility issues. You should look for a BIOS update and updates for other hardware components of your system.

Also there seems to be a certificate issue. Resetting them with pvecm updatecerts --force might help
 
I looked for BIOS updates yesterday and didn't see any. Somewhere I read that those BIOS messages are more like warnings, but I intend to follow-up.

root@proxmox1:~# pvecm updatecerts --force
(re)generate node files
generate new node certificate
Could not read private key from /etc/pve/priv/pve-root-ca.key
generating pve root certificate failed:
command 'faketime yesterday openssl req -batch -days 3650 -new -x509 -nodes -key /etc/pve/priv/pve-root-ca.key -out /etc/pve/pve-root-ca.pem -subj '/CN=Proxmox Virtual Environment/OU=6579a16d-c225-434d-b04d-8d34d5108fee/O=PVE Cluster Manager CA/'' failed: exit code 1
root@proxmox1:~# ls -l /etc/pve/priv/pve-root-ca.key
-rw------- 1 root www-data 0 Sep 14 11:47 /etc/pve/priv/pve-root-ca.key
 
root@proxmox1:~# ls -l /etc/pve
total 3
-rw-r----- 1 root www-data 451 Sep 14 11:47 authkey.pub
-rw-r----- 1 root www-data 16 Sep 14 11:30 datacenter.cfg
lrwxr-xr-x 1 root www-data 0 Dec 31 1969 local -> nodes/proxmox1
lrwxr-xr-x 1 root www-data 0 Dec 31 1969 lxc -> nodes/proxmox1/lxc
drwxr-xr-x 2 root www-data 0 Sep 14 11:47 nodes
lrwxr-xr-x 1 root www-data 0 Dec 31 1969 openvz -> nodes/proxmox1/openvz
drwx------ 2 root www-data 0 Sep 14 11:47 priv
-rw-r----- 1 root www-data 1704 Sep 14 11:47 pve-www.key
lrwxr-xr-x 1 root www-data 0 Dec 31 1969 qemu-server -> nodes/proxmox1/qemu-server
-rw-r----- 1 root www-data 127 Sep 14 11:30 storage.cfg
-rw-r----- 1 root www-data 39 Sep 14 11:30 user.cfg
drwxr-xr-x 2 root www-data 0 Sep 14 11:47 virtual-guest
root@proxmox1:~#
root@proxmox1:~#
root@proxmox1:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=8036276k,nr_inodes=2009069,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1614160k,mode=755,inode64)
/dev/mapper/pve-root on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=20110)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
/dev/nvme0n1p2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=1614156k,nr_inodes=403539,mode=700,inode64)
 
You have (for some unknown reason) empty files where your cryptographic secrets should be stored. Try moving them away.
Code: 
mv /etc/pve/priv/pve-root-ca.key /etc/pve/priv/pve-root-ca.key_old
mv /etc/pve/priv/pve-root-ca.pem /etc/pve/priv/pve-root-ca.pem_old

After that that try to regenerate them again with.
Code: 
pvecm updatecerts --force

After that look if the newly generated files have valid content. However DO NOT share the content here! They contain private, cryptographic secrets!
 
Last edited:
That got me in! Thank you

root@proxmox1:~# mv /etc/pve/priv/pve-root-ca.key /etc/pve/priv/pve-root-ca.key_old root@proxmox1:~# mv /etc/pve/priv/pve-root-ca.pem /etc/pve/priv/pve-root-ca.pem_old mv: cannot stat '/etc/pve/priv/pve-root-ca.pem': No such file or directory root@proxmox1:~# ls -l /etc/pve/priv/pve-root-ca.* -rw------- 1 root www-data 0 Sep 15 10:37 /etc/pve/priv/pve-root-ca.key_old root@proxmox1:~# pvecm updatecerts --force (re)generate node files generate new node certificate merge authorized SSH keys and known hosts creating directory '/etc/pve/firewall' for observerd files creating directory '/etc/pve/ha' for observerd files creating directory '/etc/pve/mapping' for observerd files creating directory '/etc/pve/priv/acme' for observerd files creating directory '/etc/pve/sdn' for observerd files root@proxmox1:~# ls -l /etc/pve/priv/pve-root-ca.* -rw------- 1 root www-data 3272 Sep 15 10:38 /etc/pve/priv/pve-root-ca.key -rw------- 1 root www-data 0 Sep 15 10:37 /etc/pve/priv/pve-root-ca.key_old -rw------- 1 root www-data 3 Sep 15 10:38 /etc/pve/priv/pve-root-ca.srl
 
Glad to hear!

Make sure to mark that threat as resolved then so People in the future can find an answer more easily!
 
I changed the SSD in my Proxmox server and did a clean install of Proxmox 8, and ran into the same issue.
The solution from Phillip worked, thanks! But that's quite strange.
Proxmox 7 was working fine from the get-go.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back