• 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 migrator no connection

bernhardh86

Basic Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.47
I try to migrate some stuff from Server117 to Server222. On Server222 I have installed plesk migrator and tried to connect with a password.

1664881915647.png

but I always get an error "Failed to fetch basic information about resellers, clients and domains data from source servers".

1664881978685.png

The logs says:
```
2022-10-04 13:05:53][INFO] START: Check connections
[2022-10-04 13:05:55][INFO] FINISH: Check connections
[2022-10-04 13:05:55][INFO] Check migration compatibility of source and target Plesk versions
[2022-10-04 13:05:55][INFO] Check that all required components are installed on source Plesk
[2022-10-04 13:05:55][INFO] START: Fetch basic information about resellers, clients and domains data from source servers
[2022-10-04 13:05:55][INFO] Deploy migration agent to 'x.x.x.117'
[2022-10-04 13:05:57][ERROR] 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/20221004130552/ssh-keys/id_rsa.x.x.x.117 -p 22 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no' /usr/local/psa/admin/plib/modules/panel-migrator/backend/l
ib/python/parallels/plesk/source/legacy/extras/plesk_17_0_pmm_shared/ [email protected]:/root/plesk_migrator/plesk_migrator-iwvvkm6n8x8qd7shm051qtr0ll5ql6
ao/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(228) [sender=3.2.3]

That is a critical error, migration was stopped.
```

I have tried to connect over Server222 as root to Server117 by ssh and it worked. So the credentials are correct, root login is working and there is no IP blocking:

1664882171533.png

Why is in the rsync command `-o PasswordAuthentication=no`? Doesn't this mean it tries to connect over ssh key?
 
Try to disable public key authentication in /etc/ssh/sshd_config:

Code:
PubkeyAuthentication no

And reload sshd service:

Code:
#  service sshd reload
 
You mean on the Target Server222? Have tried it now, but same issue.

Tried now the same on Source Server117, same error
 
One reason can be that the "PermitRootLogin" variable in sshd_conf (SSH configuration file) needs to be set to "yes". Many systems have it set to "no" by default so that root cannot login directly but only escalate through another user. In that case, change the setting, then reload SSH service like "service ssh reload" than it should work. After migration, set it back to "no" and reload SSH service again to increase protection of your server again.
 
Instead of enabling the global PermitRootLogin in sshd_config, you can allow it based on IP address.
Add this code at the end of sshd_config:

Match Address <IP address>
PermitRootLogin yes
 
Back
Top