Adding new service node failed with error:
'SSH communication error: Username/PublicKey combination invalid'
While adding new service node was used login name different from root.
- Was used corrupted pair public/private keys or public key was not copied on service node.
For adding new service node using private key perform the following steps:
Log in to Parallels Plesk Automation (PPA) Management node.
Generate new public and private keys pair with the command:
[root@ppa ~]# ssh-keygen -b 1024 -t dsa
Follow the instructions. Set the path to files (or leave it by default) and passphrase for the key.
Generating public/private dsa key pair. Enter file in which to save the key (/root/.ssh/id_dsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /root/.ssh/id_dsa. Your public key has been saved in /root/.ssh/id_dsa.pub. The key fingerprint is: 54:9a:6b:b1:da:6f:b3:64:8d:36:a0:8f:80:10:0b:12 firstname.lastname@example.org
Make sure the keys were created:
[root@ppa ~]# ll .ssh/ total 16 -rw------- 1 root root 612 Dec 18 04:11 authorized_keys -rw------- 1 root root 744 Dec 18 05:18 id_dsa #private -rw-r--r-- 1 root root 608 Dec 18 05:18 id_dsa.pub #public -rw-r--r-- 1 root root 394 Dec 18 04:05 known_hosts
Copy the public key to the adding service node with using command:
[root@ppa ~]# scp .ssh/id_dsa.pub email@example.com:
Note: The colon symbol means that the file will be copied in user's home folder (change it if required).
Log in to adding service node and perform the following actions:
cat id_dsa.pub >> .ssh/authorized_keys chmod 700 .ssh chmod 600 .ssh/authorized_keys ssh-agent
Log in to Parallels Plesk Automation (PPA) Administraton Panel and new service node in Top -> Infrastructure -> Service nodes -> Add New Node.
- Enter root login, select the file
'**id_dsa**'as the private key and enter the passphrase you set when generated the keys as the private key password.