• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Directadmin to Plesk Migration problem

simoncsc

New Pleskian
Server operating system version
CentOS Linux release 8.5.2111
Plesk version and microupdate number
Plesk Obsidian v18.0.59_build1800240226.11 os_Debian 12.0
hello

My Directadmin OS version is "CentOS Linux release 8.5.2111"
I can ssh to my Directadmin server via putty with root account

Now I am tring to migrate my current Directadmin to Plesk via plesk tools "Migration & Transfer Manager", but I got below error before it starts:

Failed to deploy Python on source server
Cause: Error while connecting to the the source server 'directadmin' (IP Address) at 'IP Address' by SSH as 'root': Unable to connect to 'IP Address' by SSH: [Errno None] Unable to connect to port 14686 on IP Address.
Ensure that the server is up and there are no firewall rules that may block SSH connections to the server,
then restart migration.
That is a critical error, migration was stopped.
 
Thank you for letting us know, but in this case it seems to be an issue on the source server or its firewall that does not let SSH through.
 
1. Connect to the server via SSH


2. Edit the following file on the target(Plesk) server:


/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/source/custom/actions/deploy_migrator_python.py


Append the (OSName.OS_CLOUDLINUX, '8'): 'PMM_0.1.11', line as follows:

redhat_oses = {
(OSName.OS_CENTOS, '5'): 'PMM_0.1.10',
(OSName.OS_CENTOS, '6'): 'PMM_0.1.11',
(OSName.OS_CENTOS, '7'): 'PMM_0.1.11',
(OSName.OS_CENTOS, '8'): 'PMM_0.1.11',
(OSName.OS_RHEL, '5'): 'PMM_0.1.10',
(OSName.OS_RHEL, '6'): 'PMM_0.1.11',
(OSName.OS_RHEL, '7'): 'PMM_0.1.11',
(OSName.OS_RHEL, '8'): 'PMM_0.1.11',
(OSName.OS_CLOUDLINUX, '5'): 'PMM_0.1.10',
(OSName.OS_CLOUDLINUX, '6'): 'PMM_0.1.11',
(OSName.OS_CLOUDLINUX, '7'): 'PMM_0.1.11',
(OSName.OS_CLOUDLINUX, '8'): 'PMM_0.1.11',
}

3. Re-Run the migration.



In your case make sure that the RHEL 8 line exists.
 
1. Connect to the server via SSH


2. Edit the following file on the target(Plesk) server:


/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/source/custom/actions/deploy_migrator_python.py


Append the (OSName.OS_CLOUDLINUX, '8'): 'PMM_0.1.11', line as follows:

redhat_oses = {
(OSName.OS_CENTOS, '5'): 'PMM_0.1.10',
(OSName.OS_CENTOS, '6'): 'PMM_0.1.11',
(OSName.OS_CENTOS, '7'): 'PMM_0.1.11',
(OSName.OS_CENTOS, '8'): 'PMM_0.1.11',
(OSName.OS_RHEL, '5'): 'PMM_0.1.10',
(OSName.OS_RHEL, '6'): 'PMM_0.1.11',
(OSName.OS_RHEL, '7'): 'PMM_0.1.11',
(OSName.OS_RHEL, '8'): 'PMM_0.1.11',
(OSName.OS_CLOUDLINUX, '5'): 'PMM_0.1.10',
(OSName.OS_CLOUDLINUX, '6'): 'PMM_0.1.11',
(OSName.OS_CLOUDLINUX, '7'): 'PMM_0.1.11',
(OSName.OS_CLOUDLINUX, '8'): 'PMM_0.1.11',
}

3. Re-Run the migration.



In your case make sure that the RHEL 8 line exists.
1709625728745.png
Still same issue after added the line.
 
After added the line, the error message is little diffrence before

Failed to deploy Python on source server
Cause: Command execution failed on the local server with non-zero exit code.
command: rsync -l --chmod=Fu=rw,Du=rwx,go= --timeout=30 -e 'ssh -i /usr/local/psa/var/modules/panel-migrator/sessions/20240305175030/ssh-keys/id_rsa.IP addres -p 8022 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no' /usr/local/psa/var/modules/panel-migrator/sessions/20240305175030/ssh_upload.1 root@IP addres:/etc/yum.repos.d/plesk-migrator.repo
exit code: 255
stdout:
stderr: root@IP addres: Permission denied (gssapi-keyex,gssapi-with-mic,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.
 
You mentioned that you can login to the source with PuTTY, but did you try to SSH into your source server from the target server manually, so that you can verify that basically a root login from the target to source via SSH is possible?
 
You mentioned that you can login to the source with PuTTY, but did you try to SSH into your source server from the target server manually, so that you can verify that basically a root login from the target to source via SSH is possible?
Yes I can login to source server via ssh command on traget server.
 
This is a case for a deeper investigation by support. Please open a ticket with Plesk support so that an engineer can check the issue on your server for you.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
 
Back
Top