Error: Login failed. Please try again

F

Firuz

New Member
Apr 16, 2026
10
0
1
Hello

I'm using Proxmox VE. After rebooting the server, strangely, when I connect via the proxmox graphical interface, I get the error "Login failed. Please try again", but I connect via SSH with the same password. It also works on VMs on the server. How can I fix this?
 

Attachments

  • Login failed.png
    Login failed.png
    19.8 KB · Views: 6
Please share a picture of what's behind that modal. Also run journalctl -f while you attempt to log in and share that output as well.
 
Impact said:
Please share a picture of what's behind that modal. Also run journalctl -f while you attempt to log in and share that output as well.
Click to expand...
root@az-s4:~# journalctl -f
May 02 16:19:04 az-s4 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 02 16:19:04 az-s4 systemd[1]: Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
May 02 16:19:04 az-s4 systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
May 02 16:19:04 az-s4 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4053.
May 02 16:19:04 az-s4 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 02 16:19:04 az-s4 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 02 16:19:04 az-s4 pmxcfs[703342]: [main] notice: resolved node name 'az-s4' to 'IP address' for default node IP address
May 02 16:19:04 az-s4 pmxcfs[703342]: [main] notice: unable to acquire pmxcfs lock - trying again
May 02 16:19:04 az-s4 pmxcfs[703342]: [main] notice: resolved node name 'az-s4' to 'IP address' for default node IP address
May 02 16:19:04 az-s4 pmxcfs[703342]: [main] notice: unable to acquire pmxcfs lock - trying again
May 02 16:19:14 az-s4 pmxcfs[703342]: [main] crit: unable to acquire pmxcfs lock: Resource temporarily unavailable
May 02 16:19:14 az-s4 pmxcfs[703342]: [main] crit: unable to acquire pmxcfs lock: Resource temporarily unavailable
May 02 16:19:14 az-s4 pmxcfs[703342]: [main] notice: exit proxmox configuration filesystem (-1)
May 02 16:19:14 az-s4 pmxcfs[703342]: [main] notice: exit proxmox configuration filesystem (-1)
May 02 16:19:14 az-s4 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
 
I just noticed something. This seems to be a cluster problem. Because when I type the root password of another server into another server, the GUI opens. But the inside of the server where I typed the password (PVE) is visible. In this case, how do I fix this? How do I safely dismantle the cluster?
 
In the Login dialog there is a drop-down menu to choose the "Realm". Any chance to took the wrong one?
 
UdoB said:
In the Login dialog there is a drop-down menu to choose the "Realm". Any chance to took the wrong one?
Click to expand...
I have already determined that the problem is a cluster remnant from the old cluster. Now I need to figure out how to remove it in the safest way. Since there are currently a lot of VMs on the server, it should be extremely risk-free.
 
You must log in or register to reply here.
Top Bottom
Back