[SOLVED] Proxmox VE - Login failed. Please try again.

[Scifibob]

After installing my hosts a couple of times, and more to come, I found out by accident that if you have assigned a dns hostname and using that in the browser on a fresh host, you cannot login until you have assigned a certificate on the host.
So use the ip address instead.
How about mentioning that in the login error, instead of just "Login failed. Please try again"

 

[renegade247]

Just ran into this issue after having shut down a host and recycling the parts. Something got messed up in my cluster-manager, because pvecm expected 1 did not allow me to log back into the host via web GUI. I think it was because I had configured a QDevice, although I could not remove the QDevice either because of the error:


Ultimately I had to do as @mokaz suggested, which was to destroy the cluster config for the still online node and re-create the cluster once I could get back into the web GUI:

After all that, I'm back in business, without any downtime on any VM/CT's.

thanks this worked for me

 

[Scampi]

today i visited the page of my cluster, however i was getting "Login Failed Please Try Again"


I was like: oh sh**** ive been hacked or something, googled the string about and ended up in this topic.

This totally fixed my issue => https://forum.proxmox.com/threads/proxmox-ve-login-failed-please-try-again.55488/post-437733

I was able to SSH into the machines and fix the issues
However i had to delete all "old" PVE nodes in: /etc/pve/nodes/

Runnning 8.2.2

Thx to @mokaz again !

After posting i found an alternative fix, dunno if is works or not => https://www.servethehome.com/fix-proxmox-ve-login-failed-please-try-again-on-failing-cluster/

Not fixed => https://forum.proxmox.com/threads/login-failed-but-logs-in-anyway.146754/

 

[leskovac]

This worked for me:

service pvedaemon restart
service pveproxy restart
service pvestatd restart

 

[BiteMyElbow]

I got the same error from time to time:


I did:

service pvedaemon restart
service pveproxy restart
service pvestatd restart

with no errors but no luck.

I did:

pvecm updatecerts

with output:

(re)generate node files
merge authorized SSH keys and known hosts
unable to open file '/etc/pve/priv/authorized_keys.tmp.2085777' - Input/output error

and

pvecm updatecerts --force

issued to me:

(re)generate node files
generate new node certificate
Certificate request self-signature ok
subject=OU = PVE Cluster Node, O = Proxmox Virtual Environment, CN = pve3.domain.local
Can't open "/etc/pve/nodes/pve3/pve-ssl.pem" for writing, Input/output error
00858C24477F0000:error:80000005:system library:BIO_new_file:Input/output error:../crypto/bio/bss_file.c:67:calling fopen(/etc/pve/nodes/pve3/pve-ssl.pem, w)
00858C24477F0000:error:10080002:BIO routines:BIO_new_file:system lib:../crypto/bio/bss_file.c:77:
unable to generate pve ssl certificate:
command 'faketime yesterday openssl x509 -req -in /tmp/pvecertreq-2098366.tmp -days 730 -out /etc/pve/nodes/pve3/pve-ssl.pem -CAkey /etc/pve/priv/pve-root-ca.key -CA /etc/pve/pve-root-ca.pem -CAserial /etc/pve/priv/pve-root-ca.srl -extfile /tmp/pvesslconf-2098366.tmp' failed: exit code 1

The only thing that helps in this situation is to restart the server.

Please tell me if there is another way to solve this problem without restarting the server?

 

[BiteMyElbow]

I got the same error from time to time:
View attachment 88594

I did:

service pvedaemon restart
service pveproxy restart
service pvestatd restart

with no errors but no luck.

I did:

pvecm updatecerts

with output:

(re)generate node files
merge authorized SSH keys and known hosts
unable to open file '/etc/pve/priv/authorized_keys.tmp.2085777' - Input/output error

and

pvecm updatecerts --force

issued to me:

(re)generate node files
generate new node certificate
Certificate request self-signature ok
subject=OU = PVE Cluster Node, O = Proxmox Virtual Environment, CN = pve3.domain.local
Can't open "/etc/pve/nodes/pve3/pve-ssl.pem" for writing, Input/output error
00858C24477F0000:error:80000005:system library:BIO_new_file:Input/output error:../crypto/bio/bss_file.c:67:calling fopen(/etc/pve/nodes/pve3/pve-ssl.pem, w)
00858C24477F0000:error:10080002:BIO routines:BIO_new_file:system lib:../crypto/bio/bss_file.c:77:
unable to generate pve ssl certificate:
command 'faketime yesterday openssl x509 -req -in /tmp/pvecertreq-2098366.tmp -days 730 -out /etc/pve/nodes/pve3/pve-ssl.pem -CAkey /etc/pve/priv/pve-root-ca.key -CA /etc/pve/pve-root-ca.pem -CAserial /etc/pve/priv/pve-root-ca.srl -extfile /tmp/pvesslconf-2098366.tmp' failed: exit code 1

The only thing that helps in this situation is to restart the server.

Please tell me if there is another way to solve this problem without restarting the server?

In the end, using a neural network, I was given the task of restarting the services:

systemctl restart pve-cluster pvedaemon pveproxy

And for now, the problem has been resolved. I will see if it works next time and try to write about it.

PS: When I logged in to the web interface, I noticed that I still had backup jobs running, even though it had been a long time since they started. I received the following response from the AI:
"It is understandable that restarting the pve-cluster, pvedaemon, and pveproxy services helped restore access to the web interface at the time of the backup job. In Proxmox, backup jobs processes can significantly load services, especially pmxcfs, the cluster's virtual file system that stores configuration and runs through a pve cluster.
During backup job execution, pmxcfs can work intensively with configuration data and temporarily overload, which leads to temporary suspension or even I/O errors, which causes the web interface to not respond or show a login error. Restarting services in this case "restarts" pmxcfs and related services, removing the suspended state."