Request the Login Ticket in few minutes endless

[netitgo]

Hi Team,
I am running 2 vms on PVE 6.2, and I when the PVE management tab is in the background or my hands off the keyboard, the PVE just keeps asking me to login due to the invalided ticket. The re-login time is not every 2 hours, but every several minutes.

I search the GOOGLE and got nothing could solve it and now I'm at my wit's end. Is someone there could help me out?

 

[fabian]

what does stat /etc/pve/authkey.pub /etc/pve/authkey.pub.old say? is the current time on your PVE node set correctly?

 

[netitgo]

what does stat /etc/pve/authkey.pub /etc/pve/authkey.pub.old say? is the current time on your PVE node set correctly?

root@pve:~# stat /etc/pve/authkey.pub /etc/pve/authkey.pub.old
File: /etc/pve/authkey.pub
Size: 451 Blocks: 1 IO Block: 4096 regular file
Device: 35h/53d Inode: 30 Links: 1
Access: (0640/-rw-r-----) Uid: ( 0/ root) Gid: ( 33/www-data)
Access: 2020-10-14 02:50:26.000000000 +0800
Modify: 2020-10-14 02:50:26.000000000 +0800
Change: 2020-10-14 02:50:26.000000000 +0800
Birth: -
stat: cannot stat '/etc/pve/authkey.pub.old': No such file or directory
---------------------------------------------------------
As for the system time:

root@pve:~# timedatectl
Local time: Tue 2020-10-13 22:18:44 CST
Universal time: Tue 2020-10-13 14:18:44 UTC
RTC time: Tue 2020-10-13 14:18:44
Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
root@pve:~#

thx ahead for your assistance!

 

[fabian]

yes, your time went backwards:

Local time: Tue 2020-10-13 22:18:44 CST

vs

Modify: 2020-10-14 02:50:26.000000000 +0800

you can touch /etc/pve/authkey.pub, it should reset the timestamp so that ticket validity is calculated correctly. (or wait a few hours until it has caught up anyway )

 

[netitgo]

yes, your time went backwards:

Local time: Tue 2020-10-13 22:18:44 CST

vs

Modify: 2020-10-14 02:50:26.000000000 +0800

you can touch /etc/pve/authkey.pub, it should reset the timestamp so that ticket validity is calculated correctly. (or wait a few hours until it has caught up anyway )

OK, and I did as you mentioned just now, and hopeflly it should be done!! happy to gain assistance from you!
and BTW, what will cause this issue?

 

[fabian]

this issue is caused by having a wrong system time at time of first bootup when the key is initially generated. if you update to current packages it should fix itself automatically as well.

 

[netitgo]

this issue is caused by having a wrong system time at time of first bootup when the key is initially generated. if you update to current packages it should fix itself automatically as well.

the login popup issue is gone, thank you!

your reference about the cause reminds me that it's the wrong time of my motherboard at the first bootup, but it's too late for me the adjust the motherboard time or the system time until the system is loaded, and then after a while I found this login problem, yet I didn't realize it's the wrong motherboard time caused it.

and thx so much again for getting rid of my headache!!