Can't log in to Web UI after recent update

Jan 25, 2022
12
0
6
Hi Everone,

In the last few days there were some Proxmox updates that I carried out through the Web UI on my two nodes. Everything seemed to be fine until reboot. One of the updates that I can remember to the best of m knowledge was an XML parser library update. There were also some Debian linux kernel system updates. Everything ran fine for about a day until I did a reboot (as recommended by the update script's output) and now I cannot log in to either node.

I tried a couple known workarounds:

1)
quorum {
provider: corosync_votequorum
two_node: 1
}

2) pvecm expected 1

Neither seemed to help. Even after a rebooting both nodes again.

I can access them both via SSH no issues. And I can start/stop the VMs via CLI. The VMs are also able to connect to the outside world. Corosync interface also on the same NIC. (There are no bandwidth or latency issues)

Tried this command via SSH:

curl -k -d 'username=root@pam' --data-urlencode 'password=password https://localhost:8006/api2/json/access/ticket


Got this output on node 1:

{"data":{"username":"root@pam","ticket":"PVE:root@pam:623198EA::Ia1LF3zPUaTg8qGBO3l95pesjNfqwY/pvWStooxerETFiEEQ1jLMAg6NY6C0N RGBXEQnsefA3HBolE00CyeposbyBr7qNMTnHyW9UEKqXTtg38x/f5xYGR4OW/O75SImlL6hKAPhkjlKHOA5X7qoDy+sb31wQ+VyPQiIyK0RWBnPUvL42o+Vkz6Ncw L5byeFZyauWDEx8NdC+8zNzicEwi6FXPJACFDsmujX0XFoTFuuu3VPW9hpb+tn3c1sbqJ44FONvcG5QgZZRcz5/5XWRvL3K/sQHncpO+lmk0QlEw8T6ttrOk9d6O7 02q4yESC9iyTjoEagClixcZWnGOGnrw==","CSRFPreventionToken":"623198EA:Avqb/Yy8Y/Po+w/cONTyeDnFLxwbY0wierwZEUmoy0k","cap":{"dc":{ "Sys.Audit":1,"SDN.Audit":1,"SDN.Allocate":1},"vms":{"VM.Monitor":1,"VM.Snapshot.Rollback":1,"VM.Config.Options":1,"VM.Audit" :1,"VM.Config.Disk":1,"Permissions.Modify":1,"VM.Clone":1,"VM.Migrate":1,"VM.Backup":1,"VM.Config.HWType":1,"VM.Console":1,"V M.Config.Network":1,"VM.Config.CDROM":1,"VM.Config.CPU":1,"VM.Snapshot":1,"VM.PowerMgmt":1,"VM.Config.Cloudinit":1,"VM.Alloca te":1,"VM.Config.Memory":1},"sdn":{"SDN.Allocate":1,"SDN.Audit":1,"Permissions.Modify":1},"access":{"Group.Allocate":1,"Permi ssions.Modify":1,"User.Modify":1},"storage":{"Datastore.AllocateSpace":1,"Datastore.AllocateTemplate":1,"Datastore.Allocate": 1,"Datastore.Audit":1,"Permissions.Modify":1},"nodes":{"Sys.PowerMgmt":1,"Permissions.Modify":1,"Sys.Syslog":1,"Sys.Console":


and


Got this output on node 2:

curl: (7) Failed to connect to localhost port 8: Connection refused


Tried setting setting root password to 12345 but still cannot log in via Web. And I get the curl message above still.

Any thoughts community or Proxmox team?
 
Last edited:
Node 1:

root@pve5a:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-6-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-9
pve-kernel-5.13.19-6-pve: 5.13.19-14
pve-kernel-5.13.19-5-pve: 5.13.19-13
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
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.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1



Node 2:

root@pve1a:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-6-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-9
pve-kernel-5.13.19-6-pve: 5.13.19-14
pve-kernel-5.13.19-5-pve: 5.13.19-13
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
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.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
 

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!