Resolved Plesk migration error

[Goncharenko]

Server operating system version

Ubuntu 24.04.1 LTS

Plesk version and microupdate number

Plesk Obsidian 18.0.65.2

Dear colleagues!

Could you please help me fix the problem. During the migration preparation phase, the error message shown below is displayed.
Just for information, SSH connection is possible from the new Plesk server to the old one.

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/20241128114130/ssh-keys/id_rsa.81.169.173.6 -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_12_5_pmm_shared/ [email protected]:/root/plesk_migrator/plesk_migrator-wm8ds1grsk7e0sju2j891wtmxvbiionv/pmm_agent
exit code: 255
stdout:
stderr: [email protected]: Permission denied (publickey,password).
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(231) [sender=3.2.7]

That is a critical error, migration was stopped.

Thank you in advance!

 

[Goncharenko]

Also, I can't figure out why I see -i and the location of the private key in the error logs if I chose to connect via user/password.

 

[Sebahat.hadzhi]

Could you please double-check if SSH key authentication is disabled on the source server? If needed, you can find instructions on how to do that here. As for your second question, Plesk Migrator requires SSH keys auth. It installs SSH keys during the migration. Hence, if SSH key authentication is not possible for some reason, the migration will fail as well.

 

[Goncharenko]

Could you please double-check if SSH key authentication is disabled on the source server? If needed, you can find instructions on how to do that here. As for your second question, Plesk Migrator requires SSH keys auth. It installs SSH keys during the migration. Hence, if SSH key authentication is not possible for some reason, the migration will fail as well.

Dear @Sebahat.hadzhi,

I changed the /etc/ssh/sshd_config file (PubkeyAuthentication yes) and restarted the service (sudo service ssh restart), but the issue is still exist. Please also check the detailed debug log in attachment.

 

[Sebahat.hadzhi]

Thank you, @Goncharenko. Could you please also uncomment PasswordAuthentication yes and make sure that PermitRootLogin yes is also added and uncommented? Thank you in advance.

 

[Goncharenko]

Dear @Sebahat.hadzhi,

Thanks a lot for your support.
This problem has been solved. The problem was with the private key described in the link below:

https://support.plesk.com/hc/en-us/articles/13809579796503-Migration-does-not-start-from-the-source-server-powered-by-ubuntu-14-Permission-denied-publickey-password

After generating a new key and adding it to the /root/.ssh/authorized_keys file on the source server, I successfully completed the migration preparation stage.

Have a nice weekend!
Best regards,
Igor Goncharenko