• 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!
  • 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.

Migration Question -- 8.6 to 9.2

DeanC@

Basic Pleskian
Hello! Sorry to be so dense, but I am not able to get the migration manager (9.2) to connect to the source server (8.6).

This is Linux Cent0S 5.x (new) and CentOS 4.4 (source).

The error I'm getting is "Host ... is not accessible"

Here's the thing. My server root password is different than the primary user password (using SSH I have to log in then do the su thing).

I've tried every combination of every username and password I have.

So, what combination of username/password do I use? Or could it be something else?
 
Last edited:
Okay, if I use the "primary" user and user ID, I get the following error:

Error: launchpad error (Error code = 2):
== STDERR ====================
Can't create agent directory /migration/20090912220737737/ on the remote host: sh: line 0: cd: /migration/20090912220737737/: No such file or directory
mkdir: cannot create directory `/migration': Permission denied
==============================
 
Hello,

Please, make sure that you put the root credentials at the Source Host login and password at the following step:

Home > Migration Manager > Migration Settings > Source host

Or any other user with the root credentials.

Thank you
 
For the migration process, you have to allow the login of a root user via ssh.

I normally also use "PermitRootLogin No" for ssh, but for the migration, I had to allow that.
 
Thanks akxak! I can't even esitmate how many hours I've spent trying to figure this out. I've been here, and I've tortured my server provider, who has escalated the issue to ... Plesk! They, of course, say stuff like "read the documentation." Not one of them said the magic word ... "permitrootlogin" (in the /etc/ssh/sshd_config file). Now it makes sense.

If I knew what all of the tech talk meant, and where to find everything on a server, I wouldn't need an "automated" control panel!

Thanks again, akxak.
 
Back
Top