• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Plesk Migration failed encountered RSA key, expected OPENSSH key

lucflash

New Pleskian
Hey guys,

i would like to migrate from a Debian 8 Server with Plesk to a new one with CentOS 7.
i managed the exact task multiple times last year and always used the method using ssh key file.
The error message says:

Code:
Failed to connect to the source server 'source' (XXX.XXX.XXX.XXX) by SSH: encountered RSA key, expected OPENSSH key

in /var/log/auth.log on the source server i can see:
Code:
userauth_pubkey: unsupported public key algorithm: rsa-sha2-512

i know debian 8 is out of date, but is there any chance of make a compatible call?
i tried generating new keyfile on the source server and the destination server


anyway i also tried using the name + password method with no success:

Code:
Failed to fetch basic information about resellers, clients and domains data from source servers
Cause: Command execution failed on the local server with non-zero exit code.
command: rsync -r --chmod=Fu=r,Du=rwx,go= --timeout=30 -e 'ssh -i /usr/local/psa/var/modules/panel-migrator/sessions/20220114163634/ssh-keys/id_rsa.XXX.XXX.XXX.XXX -p 22 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no' /usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/source/legacy/extras/plesk_17_0_pmm_shared/ [email protected]:/root/plesk_migrator/plesk_migrator-r9gop9voxf8bkj3jjc3my4ao24gq6dle/pmm_agent
exit code: 255
stdout:
stderr: Permission denied (publickey,password).
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.2]

That is a critical error, migration was stopped.

i can´t find any solution on the internet.
port.plesk.com/hc/en-us/articles/115000628774-Unable-to-start-Plesk-migration-due-to-invalid-permissions-on-ssh-files-Permission-denied-publickey-gssapi-with-mic- didnt work either

can someone help please?
thanks
 
I figured it out. Just for someone who is dealing with the same problem.

I checked which algorithms the source server supports with: ssh -Q kex
which was:

Code:
diffie-hellman-group1-sha1
diffie-hellman-group14-sha1
diffie-hellman-group-exchange-sha1
diffie-hellman-group-exchange-sha256
ecdh-sha2-nistp256
ecdh-sha2-nistp384
ecdh-sha2-nistp521
diffie-hellman-group1-sha1
[email protected]

then i generated new key files with ssh-keygen -t ecdsa -b 521 because ecdsa is supported.
now migration works
 
I had the same problem with CentOS7 and Ubuntu 12.
This indeed was the solution.

Only weird thing is, I never had this problem the last few months with the same version difference.
So what changed?
 
Back
Top