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

Migration Manager 'Host XXX is not accessible'

B

brendog

Guest
As stated on my last thread, I'm a newbie to all this, so please excuse my ignorance! :)

When I last upgraded my server I used Migration Manager without a problem - it was incredibly easy and worked straight away.... but not this time.

Both source and destination servers are Linux, with source using Plesk 9.2.3 and destination using 9.3. I enter all the details in the Migration Manager page on the destination server, hit 'next', but then after a few moments it just says:

Error: Host ******** is not accessible

Any suggestions? The solution found at the bottom of this thread goes way over my head - http://forum.parallels.com/showthread.php?t=89946 - I've started using putty but I'm only just getting to grips with it!
 
So, can you connect from destination server to source server as root via ssh?
 
Yes, just tried that and I can... can I migrate through SSH?
 
Do you have any errors in logs from /usr/local/psa/PMM/logs/ ? Are hostnames of both servers resolvable from one server to another and vice versa?
 
We had the same problems once and i opened a ticket for it. The problem in our case was the system locale on one of the server's... Do you use any locale settings with special character's or german umlaut's such as "äöü" and so on? If yes, set the locale to something without that. The problem was as migration manager connected to the destination server and tried to do a "df -h" on the console, the german umlaut stuff in our server couldn't be read and the above error message appeared. I also suggested that this should be somewhere in a knowledgebase article OR should be fixed, since as for example using a de-DE.UTF-8 as Locale (with german umlaut's) is quite common in germany and a lot of people use plesk.
 
Back
Top