Search results

Sometimes it helps to open the console from the developer tools in your browser: In my case I discovered a bad certificate which prevented the xhr login process from sucessfully logging in.

That helped. Thank you very much. I already restarted pve-cluster and corosync services before. The difference this time was, I powered off the forth node machine and therefore made it unavailable while restarting the services. (There was a fresh installation of Proxmox running on the forth...

All three remaining nodes show the same "pvecm status" output (except for the nodeid). Logs don't show anything noteworthy. Anything else I should/can check? Probably the 4th node afterfglow is gone after a reboot. Unfortunately rebooting the machine is not an option in my case. Quorum...

From two out of three cluster nodes the forth (dead) node has disappeared from the webui. Tried all the tricks above - no luck. On node3 the 4th node's name is still mentioned in /etc/pve/.members and /etc/pve/ha/manager_status. Is it safe to reinstall node4 (with the old name and IP addresses)...

Encountered the exact same problem, but "virtualisation" is already enabled in the BIOS. What else can I do?