[SOLVED] Login Proxmox not working

N

N33T

New Member
Nov 19, 2025
2
0
1
Hi guys,
I'm new to the forum and Proxmox. As a newbie I managed to get Proxmox working (and a few other things).
However, today I wanted to login again, but I get an Login failed: authentication failure (401) Please try again, message.
I am one-hundred-million precent sure that this is my password (using root to login).

Can I troubleshoot why login is not working? Logs? I am so lost, anyone who can show a newbie the/a way in these kind of scenarios?

I'm sure that I'm not the first and only problem with this issue but all the topics are also related to people who tried stuff and edited some important files, which is why they can't login. I tried nothing and changed nothing..
 
Last edited:
do you have other means to access the system (SSH, IPMI, ..)? do those work?
 
Hi, @N33T .
I guess you're talking about logging in the web GUI (https://ip.ad.dr.ess:8006).

In the 3rd line of the login form (named "Realm") there's a drop-down menu.

Sometimes it is auto-selecting "Proxmox VE authentication server" instead of "Linux PAM standard authentication" in which of course your password doesn't match.

So: pay attention to select "Linux PAM standard authentication".

Does it work for you then? I'm asking because there can be some other reason, of course.
 
having the same trouble all of a sudden. journalctl shows this:


Code: 
Nov 25 13:13:04 pve01 pvestatd[2512]: authkey rotation error: cfs-lock 'authkey' error: got lock request timeout
Nov 25 13:13:04 pve01 pvestatd[2512]: status update time (9.203 seconds)
Nov 25 13:13:11 pve01 pvescheduler[3001392]: jobs: cfs-lock 'file-jobs_cfg' error: got lock request timeout
Nov 25 13:13:11 pve01 pvescheduler[3001391]: replication: cfs-lock 'file-replication_cfg' error: got lock request timeout
Nov 25 13:13:14 pve01 pvestatd[2512]: authkey rotation error: cfs-lock 'authkey' error: got lock request timeout
Nov 25 13:13:14 pve01 pvestatd[2512]: status update time (9.161 seconds)
Nov 25 13:13:24 pve01 pvestatd[2512]: authkey rotation error: cfs-lock 'authkey' error: got lock request timeout
Nov 25 13:13:24 pve01 pvestatd[2512]: status update time (9.192 seconds)
Nov 25 13:13:34 pve01 pvestatd[2512]: authkey rotation error: cfs-lock 'authkey' error: got lock request timeout
Nov 25 13:13:34 pve01 pvestatd[2512]: status update time (9.208 seconds)
Nov 25 13:13:45 pve01 pvestatd[2512]: authkey rotation error: cfs-lock 'authkey' error: got lock request timeout
Nov 25 13:13:45 pve01 pvestatd[2512]: status update time (9.203 seconds)
Nov 25 13:13:54 pve01 pvestatd[2512]: authkey rotation error: cfs-lock 'authkey' error: got lock request timeout
Nov 25 13:13:54 pve01 pvestatd[2512]: status update time (9.212 seconds)
 
is this a cluster? check the cluster status, this sounds like something is broken there..
 
Unfortunately this issued hasn't been solved in this thread. We are hitting the same problem with PVE 9.1.9.

Code: 
Apr 27 11:12:10 pve01 pvedaemon[3942]: authentication failure; rhost=::ffff:172.16.224.10 user=root@pam msg=cfs-lock 'authkey' error: got lock request timeout
Apr 27 11:15:57 pve01 IPCC.xs[1450164]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:172.16.224.10  user=root
Apr 27 11:15:59 pve01 pvedaemon[3940]: authentication failure; rhost=::ffff:172.16.224.10 user=root@pam msg=Authentication failure
Apr 27 11:16:19 pve01 pvedaemon[3942]: authentication failure; rhost=::ffff:172.16.224.10 user=root@pam msg=cfs-lock 'authkey' error: got lock request timeout
Apr 27 11:17:48 pve01 pvedaemon[3940]: authentication failure; rhost=::ffff:172.16.224.10 user=root@pam msg=cfs-lock 'authkey' error: got lock request timeout
Apr 27 11:17:53 pve01 pvedaemon[3942]: authentication failure; rhost=::ffff:172.16.224.10 user=root@pve msg=no such user ('root@pve')
Apr 27 11:18:37 pve01 pvedaemon[3942]: authentication failure; rhost=::ffff:172.16.224.10 user=root@pam msg=cfs-lock 'authkey' error: got lock request timeout
Apr 27 11:19:10 pve01 pvedaemon[3941]: authentication failure; rhost=::ffff:172.16.224.10 user=root@pam msg=cfs-lock 'authkey' error: got lock request timeout
Apr 27 11:19:26 pve01 pvedaemon[3940]: authentication failure; rhost=::ffff:172.16.224.10 user=root@pam msg=cfs-lock 'authkey' error: got lock request timeout

There is one attempt to login with pve@pam, which of course also didn't work.

I checked the file system and saw that /var/lib/vz was running out of space (99% used). This was, because someone had mistakenly, configured the backup location to be the local drive, instead of the backup server. I hope this issue is resolved for now. Maybe this helps somebody else, or maybe there is another issue we're hitting.
 
the messages indicate that the cluster is not quorate.. did the root partition maybe also run out of space? check the logs of corosync and pve-cluster please!
 
fabian said:
the messages indicate that the cluster is not quorate.. did the root partition maybe also run out of space? check the logs of corosync and pve-cluster please!
Click to expand...
Hi Fabian.,
this is a single node and not part of a cluster, thus a quorum should not be necessary. I also just checked out monitoring: The root partition has never run out of space.
 
then please check and post the logs of the two services I mentioned!
 
You must log in or register to reply here.
Top Bottom
Back