Proxmox uses the root account over SSH for its operations. Make sure the root public ssh key (id_rsa.pub) of Proxmox1 is in the authorized_keys for root on Proxmox2
I agree but I didn't know how to do this. So I did some more Googling and found this command and ran it on the node that was not working (Proxmox2):
cat /var/log/auth.log
In amongst many other messages was this one:
Authentication refused: bad ownership or modes for directory /etc
Using that message and some more Googling I found this posting:
https://serverfault.com/questions/2...ys-permission-denied-publickey-password-error
fixed my problem. So need change 775 to 755 on user home directory. If anyone know reason why 775 is bad please comment..
share edit follow
answered Feb 3 '11 at 17:26
Alexander Ovchinnikov
18322 gold badges22 silver badges1010 bronze badges
I do not have enough reputation to comment, so this goes in a separate answer. The reason that you had to change the permissions to 755 is that you have StrictMode set to yes, which means: StrictModes yes The option StrictModes specifies whether ssh should check user's permissions in their home directory and rhosts files before accepting login. This option must always be set to yes because sometimes users may accidentally leave their directory or files world-writable. From faqs.org/docs/securing/chap15sec122.html – user60129 Feb 4 '11 at 7:42
Group write permissions are bad, if the users homedir belongs to say, group 'staff' or 'users'. – Alex Holst Feb 4 '11 at 8:29
So I looked at the 2 nodes that were working and found out via properties that the permissions were 0755. I looked at the permissions for the node that wasn't working and the /etc directory had permissions of 1777.
Don't know how, when or why it was changed.
So with a little more digging: chmod 755 /etc
Now, finally things are working again.
Thanks for all the help,
Tom
