[SOLVED] GUI interface, showing login failed, please try again

[Avinia]

2 weeks ago, I installed 3 virtual machines on PVE, and they were running normally. Until the day before yesterday, the GUI interface suddenly failed to log in, and the login failed, please try again.

The following is the relevant error message

root@pve:/# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2023-04-05 00:02:27 CST; 8min ago
Process: 201393 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 201413 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 201418 (pveproxy)
Tasks: 4 (limit: 9246)
Memory: 192.6M
CPU: 2.624s
CGroup: /system.slice/pveproxy.service
├─201418 pveproxy
├─201419 pveproxy worker
├─201420 pveproxy worker
└─201421 pveproxy worker

Apr 05 00:02:25 pve systemd[1]: Starting PVE API Proxy Server...
Apr 05 00:02:27 pve pveproxy[201418]: starting server
Apr 05 00:02:27 pve pveproxy[201418]: starting 3 worker(s)
Apr 05 00:02:27 pve pveproxy[201418]: worker 201419 started
Apr 05 00:02:27 pve pveproxy[201418]: worker 201420 started
Apr 05 00:02:27 pve pveproxy[201418]: worker 201421 started
Apr 05 00:02:27 pve systemd[1]: Started PVE API Proxy Server.


root@pve:/# systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2023-04-04 00:13:35 CST; 23h ago
Process: 962 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 991 (pvedaemon)
Tasks: 4 (limit: 9246)
Memory: 137.1M
CPU: 18.269s
CGroup: /system.slice/pvedaemon.service
├─991 pvedaemon
├─992 pvedaemon worker
├─993 pvedaemon worker
└─994 pvedaemon worker

Apr 04 00:13:35 pve pvedaemon[991]: worker 992 started
Apr 04 00:13:35 pve pvedaemon[991]: worker 993 started
Apr 04 00:13:35 pve pvedaemon[991]: worker 994 started
Apr 04 00:13:35 pve systemd[1]: Started PVE API Daemon.
Apr 04 00:14:46 pve pvedaemon[993]: authentication failure; rhost=::ffff:10.10.10.21 user=root@pve msg=no such user ('root@pve')
Apr 04 00:16:04 pve pvedaemon[992]: authentication failure; rhost=::ffff:10.10.10.21 user=root@pve msg=no such user ('root@pve')
Apr 04 23:19:11 pve pvedaemon[993]: authentication failure; rhost=::ffff:10.10.10.21 user=root@pve msg=no such user ('root@pve')
Apr 04 23:50:42 pve pvedaemon[993]: authentication failure; rhost=::ffff:10.10.10.21 user=root@pve msg=no such user ('root@pve')
Apr 05 00:02:44 pve pvedaemon[992]: authentication failure; rhost=::ffff:10.10.10.21 user=root@pve msg=no such user ('root@pve')
Apr 05 00:03:26 pve pvedaemon[993]: authentication failure; rhost=::ffff:10.10.10.21 user=root@pve msg=no such user ('root@pve')


root@pve:/# journalctl -f
-- Journal begins at Mon 2022-03-21 03:55:25 CST. --
Apr 05 00:02:25 pve systemd[1]: Stopped PVE API Proxy Server.
Apr 05 00:02:25 pve systemd[1]: pveproxy.service: Consumed 25.776s CPU time.
Apr 05 00:02:25 pve systemd[1]: Starting PVE API Proxy Server...
Apr 05 00:02:27 pve pveproxy[201418]: starting server
Apr 05 00:02:27 pve pveproxy[201418]: starting 3 worker(s)
Apr 05 00:02:27 pve pveproxy[201418]: worker 201419 started
Apr 05 00:02:27 pve pveproxy[201418]: worker 201420 started
Apr 05 00:02:27 pve pveproxy[201418]: worker 201421 started
Apr 05 00:02:27 pve systemd[1]: Started PVE API Proxy Server.
Apr 05 00:02:44 pve pvedaemon[992]: authentication failure; rhost=::ffff:10.10.10.21 user=root@pve msg=no such user ('root@pve')

 

[BobhWasatch]

What failed to login? The PVE host? If the login screen appears but you can't log in perhaps you have the wrong realm selected. That's the dropdown under the password entry box.

ETA: The error message is for "root@pve". I think that means you have the PVE relam selected rather than Linux PAM.

 

[Avinia]

What failed to login? The PVE host? If the login screen appears but you can't log in perhaps you have the wrong realm selected. That's the dropdown under the password entry box.

ETA: The error message is for "root@pve". I think that means you have the PVE relam selected rather than Linux PAM.

Yes, I have always used the PVE method to log in with the root account, and did not choose the Linux PAM login method, but a prompt will pop up when I start to log in two days ago, the login failed, please try again

 

[B.Otto]

Yes, I have always used the PVE method to log in with the root account, and did not choose the Linux PAM login method, but a prompt will pop up when I start to log in two days ago, the login failed, please try again

Are you sure about this? By default only PAM has the user root. So unless you have manually created another user "root" in the realm PVE, there should only be a user root@pam - which would fit to your error message, since there does not seem to be a user root@pve in your Proxmox server

 

[Avinia]

Are you sure about this? By default only PAM has the user root. So unless you have manually created another user "root" in the realm PVE, there should only be a user root@pam - which would fit to your error message, since there does not seem to be a user root@pve in your Proxmox server

Sorry, I just checked. I read it wrong. I used the Linux PAM method to log in before, but now I use the root account to log in in this way, and it still prompts that the login failed, please try again.

 

[Avinia]

My God, the problem has been solved, I found out that my chrome browser problem caused it, when I changed the browser and tried again, the problem can be solved

 

[naimi]

soft resetting the whole server fixed this error for me