TASK ERROR: Failed to run vncproxy.

[mhayhurst]

Thanks to some folks in the IRC channel, I finally fixed this (at least partially: the remote Web console works again) by doing the following on the node whose Web page I'm connected to:

ssh -o HostKeyAlias=IPv4.address.of.other.node IPv4.address.of.other.node
ssh -o HostKeyAlias=IPv6.address.of.other.node IPv6.address.of.other.node
ssh -o HostKeyAlias=HostnameOfOtherNode HostnameOfOtherNode

For each one, delete the entry in /root/.ssh/known_hosts it complains about

Glad it worked but this was mentioned in my Post #12:

rm ~/.ssh/*

I even say:

Believe it or not, starting with a clean slate again...

Did you try: "starting with a clean slate" as I discussed and then executing:

pvecm updatecerts

?

 

[Pegasus]

Did you try: "starting with a clean slate"

No, I guess I glossed over your reply thinking there were still problems mentioned at the end of it. Plus, I was hesitant to remove everything afraid it will mess something else up, since I don't know everything 'pvecm updatecerts' does. I will try your "clean slate" steps next time though, since it appears that command re-creates exactly what your steps delete. Thank you for the reply!

 

[srslol]

can you ssh without any password as root from Proxmox1 to Proxmox2 (and the other direction)?
PVE relies on ssh-public-key auth for some of its operations (including the vncproxy).

In any case you can try running `pvecm updatecerts` and see if this helps.

This solution worked for me! I did this on all new nodes. Woo hoo.

 

[alecmedina]

can you ssh without any password as root from Proxmox1 to Proxmox2 (and the other direction)?
PVE relies on ssh-public-key auth for some of its operations (including the vncproxy).

In any case you can try running `pvecm updatecerts` and see if this helps.

This was my solution for the same issue.