• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx

  • We are developing a new feature in Plesk that will help you promote your websites or business on social media. We want to conduct a one-hour online UX test to present the prototype and collect feedback. If you are interested in the feature, please book a meeting via this link.
    Thank you in advance!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk Migration Manager

JamieGregory

New Pleskian
Hey,

I currently have a VPS with GoDaddy and I have just recently bought a dedicated server at Rackspace.

(VPS has Plesk Panel version 11.0.9 and my dedicated server has a Plesk Plan version 11.5.30)

I'm trying to migrate EVERYTHING over in one go (about 16GB worth of content) and I have filled in the initial 'logging into your other server' page and I have been greeted with the following page:

However it has been stuck on this page for the last 12 hours. Is this normal? As it doesn't seem this is even the actual file transfer stage yet?

Please advise!
Jamie
 
Last edited:
I would not expect it to take that long. 16Gb is not a lot. I've migrated server servers with more data than that. It takes a while but not a significant amount of time (minutes not hours) to get past the bit you seem to be stuck on.

So.....

Make sure port 22 is open on the old server to the IP of the new server.

Take a look at http://kb.parallels.com/en/113586 if you have not done so already. There's a lot of useful info there.

Also note one of the new features in Plesk 11.5:
•The updated migration manager is designed to identify possible transfer limitations in advance, allowing you to configure new servers with the correct services, disk space and other resources before starting the transfer process.
•During transfers, a new and streamlined process will now communicate errors in a way that is easier to identify and react to, and will help with troubleshooting by keeping all relevant logs in a single dedicated folder. For example, everything about recent transfers will be stored in /usr/local/psa/PMM/logs/migration-2013-04-10-19-39-22-557/.

But I'm not sure there will be anything significant in the logs. Worth checking anyway.

I'd check /var/log/messages on the old VPS as well as on the new VPS when it gets stuck.

Also you can cancel the process and restart -- it might just come to life the second try.

However, I'd give it a few more hours, just in case it bursts into life.
 
Hi Faris,

Thanks for your reply.

I found out what my issue was. It was caused by GoDaddy's VPS' having their default settings to automatically switch off root access so I had to change that through SSH and vim editor.

Now my files have transferred over, however, ALL my WordPress passwords have changed? And some of my websites have broken big time e.g. www.EquityReleaseCalculator.net / Should look like:

Do you have any idea what could of caused this?

Does Plesk migrate all the databases too? As I'm even missing pages that I've spent days writing text for :(

Thanks,
Jamie
 
Last edited:
Yes, every last iota of data gets transferred. Passwords don't get changed.

Were there any errors listed in the Migration log?

Now, for wordpress sites, I recently came across an interesting situation which MAY be what's happened in your case (and is easy to resolve).

IF you installed the original wordpess script using APS then later did some manual changes (for example changed database), then Plesk will revert the wp-config.php to reflect the original admin password and database. This is expected behaviour in a way, but it can catch you out!

I'm really hoping this is what's happened for you because it is nice and easy to resolve - just edit wp-config.php (check on your old server to see what it has there and make everything match. The salt may need to be changed to match too in some circumstances, but probably not)
 
I've just checked the migration log and some of the connections had timed out with the old server so I re-ran the migration and everything completed smoothly. No problems. However, the site still looks faulty.

As all these sites run on Plesk, all their WordPress installations were done through the Plesk > Application area - is this APS?

I have just copied the whole wp-config.php file from my old server and pasted it into the wp-config.php file on the new server, refreshed the website and it still remains faulty.

So I compared the two files and the only things that are different to one another are the:

define('AUTH_KEY',
define('SECURE_AUTH_KEY',
define('LOGGED_IN_KEY',
define('NONCE_KEY',
define('AUTH_SALT',
define('SECURE_AUTH_SALT',
define('LOGGED_IN_SALT',
define('NONCE_SALT',

Lines + all their rubbish after them^

Any other suggestions?
 
I've just redirected my host name back towards my old server that still has all the original files and the website still looks faulty!

It's as if the migration has corrupted something? Is this possible?
 
No, Migration Manager does not touch any data on your old server. It just copies it to the new one.
Are you sure you were looking at the old sites on the old server and not still looking at the new ones?

Maybe look at your php.ini and make sure there's nothing significantly different on the new verses the old which might be causing this.
Check the error logs for the sites to see if there are any unusual errors.

Also could some sort of update have caused the problem? Your browser might have changed? Something updated on both servers? Php version update?

None of this explains the missing text from your recent update. check page source to make sure it really is missing and not just hidden?
 
Back
Top