• 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] Internal Plesk Migrator error: 'No module named paramiko', migration is aborted.

linuxKurt

Basic Pleskian
Server operating system version
ubuntu 22.04
Plesk version and microupdate number
18.0
I am on my fourth migration trial today. I am scheduled to do a Production Migration this evening.

I went into the server and started the Plesk Migrator Extension and I am getting this error. I successfully ran a migration on this server 3 days ago and nothing really has changed surrounding the server or anything installed on it. After the migration we did some WordPress and vBulletin configurations, but did nothing related to PHP or anything that was installed when the migrator ran.

I checked today and python3-paramiko is installed and the newest version. I am not sure where to go from here. Maybe Plesk Migrator is looking for a different version?



1683746846017.png1683746453752.png
 
Does this article help?
It's a different error, but there seems to be a plesk-py27-paramiko_2.7.1 package. Maybe that's what the migrator is reporting errors about.

Thanks, I have been looking at this, I don't really understand, I am going to re-image my server and start over.
 
Does this article help?
It's a different error, but there seems to be a plesk-py27-paramiko_2.7.1 package. Maybe that's what the migrator is reporting errors about.

I got my server reset and updated all certificates and public keys in SSH. Restarted SSH on both servers. I am now getting the following error. It looks incomplete, meaning there must be more to the error.


1683757766076.png
 
Thanks for everyone's input, turns out that I once I added the public key to the authorized key file, I was able to connect. I don't understand why placing the public key in the .ssh directory and restarting the sshd service does not update that file. Anyway, problem solved and hopefully this will be my last plesk migration for a while. RESOLVED>
 
Back
Top