• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Plesk Migrator Authorization SSH key from cPanel

tanasis

Regular Pleskian
Hello,
I did this Authentication by SSH (Linux)

[root@server ~]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): 512key
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in 512key.
Your public key has been saved in 512key.pub.
The key fingerprint is:
SHA256:q18N..................Cw4 [email protected]
The key's randomart image is:
+---[RSA 3072]----+
| |
....................
| .o+==O== |
+----[SHA256]-----+

[root@server ~]# ssh-copy-id [email protected]
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '1xx.2xx.2xx.1x (1xx.2xx.2xx.1x)' can't be established.
ECDSA key fingerprint is SHA256:vR+R...........................................++OYo.

What am I doing wrong ?
 
Does the server to where you want to write the key allow root access through SSH (PermitRootLogin = yes)?
 
If that was the cause, I suggest to limit root login to the target server only, e.g. set the general PermitRootLogin variable to "no", but add two lines to the end of the file:
Code:
Match Address <IP address of the target>
PermitRootLogin yes
This way only the target will be allowed to login by root, but no other ip.
 
Back
Top