WebUI accessible, but login does not work correctly

[coyote]

Hey, I have a small problem. First the initial situation:

2 Intel NUC's, one with Proxmox installed directly, on the second one Debian Desktop and Proxmox on top.
So far it has run without any problems, but today I had to import a timeshift from yesterday on the Debian desktop.
Now the box is running as well as the LXC and the VM on the NUC, but I can't access the Proxmox WebUI from this NUC or the other one.
Login is displayed, I try to log in with root (as always), then the login field disappears briefly and comes back immediately.

After the first login attempt, I get the following error: Connection error 401,permission denied, invalid PVE ticket
Here is another screenshot:

root@debianNUC:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.13-1-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx8
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.1
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.5-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve2

SSH works without any problems. I hope you can help me, I have no idea what went wrong during the timeshift.

 

[coyote]

systemctl status pve-daemon

Login ok, but WebUI does not work.

"systemctl reload-or-restart pvedaemon.service" also does not work.

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
     Active: active (running) since Fri 2024-03-08 13:43:35 CET; 3h 43min ago
   Main PID: 3617 (pvedaemon)
      Tasks: 4 (limit: 8908)
     Memory: 186.8M
        CPU: 5.026s
     CGroup: /system.slice/pvedaemon.service
             ├─3617 pvedaemon
             ├─3618 "pvedaemon worker"
             ├─3619 "pvedaemon worker"
             └─3620 "pvedaemon worker"

Mär 08 15:14:08 debianNUC pvedaemon[3620]: <root@pam> successful auth for user 'root@pam'
Mär 08 15:52:51 debianNUC pvedaemon[3618]: <root@pam> successful auth for user 'root@pam'
Mär 08 15:52:57 debianNUC pvedaemon[3619]: <root@pam> successful auth for user 'root@pam'
Mär 08 15:53:36 debianNUC pvedaemon[3618]: <root@pam> successful auth for user 'root@pam'
Mär 08 15:53:44 debianNUC pvedaemon[3619]: <root@pam> successful auth for user 'root@pam'
Mär 08 16:02:21 debianNUC pvedaemon[3620]: <root@pam> successful auth for user 'root@pam'
Mär 08 16:02:30 debianNUC pvedaemon[3619]: <root@pam> successful auth for user 'root@pam'
Mär 08 16:44:56 debianNUC pvedaemon[3619]: <root@pam> successful auth for user 'root@pam'
Mär 08 16:45:03 debianNUC pvedaemon[3620]: <root@pam> successful auth for user 'root@pam'
Mär 08 17:26:59 debianNUC pvedaemon[3618]: <root@pam> successful auth for user 'root@pam'

 

[coyote]

looks like root is logged out immediately, but why?

root@debianNUC:~# tail -n 10 /var/log/auth.log
2024-03-08T17:00:01.902253+01:00 debianNUC CRON[196092]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
2024-03-08T17:00:02.428364+01:00 debianNUC CRON[196092]: pam_unix(cron:session): session closed for user root
2024-03-08T17:09:01.438245+01:00 debianNUC CRON[204757]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
2024-03-08T17:09:01.440474+01:00 debianNUC CRON[204757]: pam_unix(cron:session): session closed for user root
2024-03-08T17:17:01.449435+01:00 debianNUC CRON[212393]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
2024-03-08T17:17:01.452126+01:00 debianNUC CRON[212393]: pam_unix(cron:session): session closed for user root
2024-03-08T17:30:01.462565+01:00 debianNUC CRON[224792]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
2024-03-08T17:30:01.464422+01:00 debianNUC CRON[224792]: pam_unix(cron:session): session closed for user root
2024-03-08T17:39:01.473722+01:00 debianNUC CRON[233309]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
2024-03-08T17:39:01.475647+01:00 debianNUC CRON[233309]: pam_unix(cron:session): session closed for user root

 

[BobhWasatch]

That is cron, not an interactive login.

Is the time set correctly on the PVE machine and on the client you are accessing it with? The error you are getting is usually caused by client and server disagreeing about the time. Is the PVE machine's BIOS set to UTC as it should be? That last thing is usually why the time is wrong after the spring time change.

 

[coyote]

That is cron, not an interactive login.

Is the time set correctly on the PVE machine and on the client you are accessing it with? The error you are getting is usually caused by client and server disagreeing about the time. Is the PVE machine's BIOS set to UTC as it should be? That last thing is usually why the time is wrong after the spring time change.

I think it's not different:

root@pve:~# date
Fr 8. Mär 19:51:21 CET 2024

Same on both machines and also on client. This login error has been there, since I installed the timeshift backup today on the Debian system

 

[coyote]

Hardware clock also matches, any idea?

 

[BobhWasatch]

I misunderstood your original post. Never heard of timeshift before.

So you restored to a previous state using a third party software? Maybe look at what it restored or didn't restore. There could be some version skew.

 

[coyote]

Yes, Timeshift is on Debian Desktop. There was a Backup from yesterday. Proxmox is installed on Debian Desktop on this machine. Proxmox runs fine so far on both machines, all VM's and LXC's work as it should. The only thing is, that I can't login in WebUI. SSH works fine on both machines. I don't no why login not work on both machines, not just the one where I imported the backup

 

[BobhWasatch]

My guess would be that timeshift did not correctly roll back something important to the web GUI. I have no idea what that might be though.

 

[coyote]

Ok, hopefully someone else can help me. It's pretty garbage as it is and I don't really want to re-install both machines as all my home automation is running on them

 

[coyote]

I have no idea why, but since today the login works again without any problems. That's strange. Problem solved by itself.

 

[maowens]

I had the same issue. My concern was hostname changed twice (yes twice) and I cleared out /var/lib/rrcache/db/ and /etc/pve/pve2-nodes upon reboot I could see my web-ui not coming up with the error invalid pve ticket. I hit refresh and everything came back.