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

Instance broken after migration

Denis Gomes Franco

Regular Pleskian
Hey everyone,

Thought about posting this so others that are having the same problem can have the solution. Also this may serve as feedback to the developers.

I'm in the process of migrating dozens of Wordpress sites from my old server to the Plesk platform. Since the Website Import extension does not seem to work even though I have SSH access to the old server (I also posted a thread about this but no solution so far) then I'm using the trusted (and best, IMHO) Duplicator plugin.

--- By the way here's another feedback: as Plesk is focusing on Wordpress, why not develop a Wordpress plugin to *push* a Wordpress installation *to* the Plesk server? I understand that Plesk users are technically minded but that would make it very easy for novice users without having to worry about SSH or FTP access on their old server. Cloudways did just that with their Blogvault partnership.

After migration and checking that the site is working, I then proceed to add it to the Wordpress toolkit. But almost every single time it return with a INSTANCE BROKEN error. Digging deeper I found out that the problem is usually because in wp-config.php there is a require('wp-salt.php'); directive and Wordpress toolkit borks at that saying that this file could not be accessed or something like that, even though this file is actually present in root and the site is working just fine. I really can't understand why is this happening, as there are no permission issues stopping the file from running.

So my solution to this is to open https://api.wordpress.org/secret-key/1.1/salt/ to get new salts, and then replace the require(); above with these. After this, I just need to detach the instance and scan again to make it work.
 
Back
Top