• 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 Error migrating tool

SalvadorS

Regular Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.68
Hello,

I starting receiving this error when I try to use the migration tool:

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/20250329081054/ssh-keys/id_rsa.x.y.z.a -p xx -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-e6jimuvwpzgx5ysj5qnjjysy5x54rajq/pmm_agent
exit code: 30
stdout:
stderr: [sender] io timeout after 30 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(201) [sender=3.2.7]

That is a critical error, migration was stopped.

The destination server is a new server and I never receive this error before....

I check it two different days always the same
 
Hello, @SalvadorS . Are you able to establish a successful SSH connection from the source server to the target server without the migrator, please? The error could result from a connectivity issue.
 
Hello @Sebahat.hadzhi and thanks a lot for your reply.

Yes, I can connect via SSH to the server. In fact the error is after I select the domains to transfer, so there is a initial connection....
 
Thank you for the confirmation. Could you please also try:

nmap source-server-IP -Pn -p22
traceroute -T source-server-IP

and confirm if you notice any connectivity issues? Also, could you please confirm what type of website you are attempting to migrate?
 
Hello,

Thanks again @Sebahat.hadzhi for your reply.

I can do that without any problem from the destination server:

Starting Nmap 7.93 ( Nmap: the Network Mapper - Free Security Scanner ) at 2025-03-31 13:00 CEST

Nmap scan report for servername (IP)

Host is up (0.00036s latency).

PORT STATE SERVICE

xxx/tcp open emsd-port

MAC Address: XXX

Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds


traceroute to IP (IP), 30 hops max, 60 byte packets
1 servername (IP) 0.151 ms 0.152 ms 0.163 ms

Regarding type of website is a normal one, mail web... nothing special.

Is it possible that in the latest version of Plesk 18.0.68 there is some kind of problem with the migration tool? The Plesk firewall is enabled on both servers (allowing SSH access from the corresponding IPs), but even disabling it, the problem remains the same.
 
Thank you for the update and the provided details. This doesn't sound like an issue with the migrator to me. That error is observed due to poor network connection between the servers, which is something common. Although from the provided details doesn't seem like there's nothing obvious, at least with the first hop, that's not guarantee there isn't internment connectivity issue. If you have the option to get in touch with our support team, that will be my advise so they can connect to both servers and perform tests. If not, what I can recommend is to try creating a wrapper for rsync (at your own risk):

# mv /usr/bin/rsync /usr/bin/rsync_orig
# touch /usr/bin/rsync
# printf '#!/bin/bash\n/usr/bin/rsync_orig \"$@\"\nsleep 5\n' > /usr/bin/rsync
# chmod 0755 /usr/bin/rsync
 
Back
Top