• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Migration error using SSH Keys "Failed to connect to the source server 'source' ('X.X.X.X') by SSH:

TurnKeyWebsites

New Pleskian
Hello

System Details:
Plesk Onyx v17.0.17_build1700161028.14 os_Ubuntu 16.04

Problem: Attempt to Migrate using Authorization = SSH keys

Full Error:
"Failed to connect to the source server 'source' ('X.X.X.X') by SSH: not a valid EC private key file"

What works:
Migration in either direction between the 2 VPSs using Authorization = User/password

SSH keys have been setup in both directions. Can login to each server from the other using SSH keys. (using root right now for testing)

Other: Both VPSs are the same (Plesk Onyx v17.0.17_build1700161028.14 os_Ubuntu 16.04)

Keys details:
ssh-keygen -t rsa -b 4096

Thank You
 
Same issue.

I'm trying to migrate from:

CentOS 6.8 (Final)‬ / Plesk version 12.5.30 Update #55

to

CentOS Linux 7.3.1611 (Core) / Plesk Onyx Version 17.0.17 Update #11


Failed to connect to the source server 'source' (x.x.x.x) by SSH: not a valid EC private key file

:(
 
Hello!

In the most common case, such error (not a valid EC private key file) occurs because the path to the private key file specified incorrectly. Could you please check the following:

1. The absolute path to the private RSA key on the target Plesk server (the same server where Plesk Migrator installed) specified in the "SSH key (on target server)" field of migration configuration form. Usually it is '/root/.ssh/id_rsa'.
2. The file at the specified path exists.
3. Private RSA key created without the passphrase.

If it doesn't help, we can investigate the root cause and provide a solution, if you provide me (via private conversation) the access to your target Plesk server.
 
Hello, and thank you.
Your suggestion worked. The user has to be root and the passphrase has to be blank, with these conditions met, it worked fine.
 
Hello! Glad, I could help. :)

Also, I create an issue PMT-3364: we will provide the clear instruction how to configure interaction with source server using SSH keys both in GUI and documentation. Thank you for feedback!
 
Back
Top