• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Migration Questions?

S

seanstephens

Guest
We have an existing client on one of our plesk servers. He has about 20 sites who he has just started hosting with us. However we want to move him to his own server. Because the clients JUST started to host with him/us we dont want to have any downtime while this happens. So, whats the best method to accomplish this? Should we use the migration manager, or use a dump? The dump lets us migrate IP's while the mirgation manager doesnt. Which might be a better option, because we dont want to have to change name servers in the TLD's. Anybody have any experience with this sort of stuff? Any and all ideas are welcome. Thanks
 
You can use the dump or the migration manager, it does not matter. After you make the move you must change the IPs of the domains on the old server DNS. Then you can change the nameservers to the new server and clients will not face DNS issues.
 
Back
Top