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

Issue Clone this instance

NicolasP.

Regular Pleskian
I am trying to use "Wordpress -> Clone this instance" and I am getting this error.

clone.jpg

I tried to do it with other wordpress sites and nothing happened.

Plesk Onyx Version 17.5.3 Update #13
CentOS Linux 7.3.1611
 
Hello Nicolas,

I cannot reproduce this issue. Could you please provide me with more details?

Hello.

You just go to a Wordpress Domain. You will see Clone on top of this page (under File Manager - Mail - Databases)

Choose where you want to clone this domain and maybe you will see this error.

It is the first time I need to clone a Wordpress Website within Plesk, but it gives me this strange error
 
Looks like WordPress Toolkit unable to dump database of your source WordPress instance using access credentials, retrieved from the wp-config.php of this instance. The initial issue EXTWPTOOLK-636 fixed in WordPress 2.2.0 (WordPress Toolkit - Plesk Extensions):

[-] If cloning of a WordPress installation was blocked by database import or export errors, the WordPress Toolkit reported that the installation was not configured, but did not explain the actual problem. Now it correctly detects and reports the problem that caused the error. (EXTWPTOOLK-636)

So, at now you get an actual error which block the cloning process. Could you please check ability to connect to database of your source WordPress manually with credentials, specified in wp-config.php?
 
Looks like WordPress Toolkit unable to dump database of your source WordPress instance using access credentials, retrieved from the wp-config.php of this instance. The initial issue EXTWPTOOLK-636 fixed in WordPress 2.2.0 (WordPress Toolkit - Plesk Extensions):

[-] If cloning of a WordPress installation was blocked by database import or export errors, the WordPress Toolkit reported that the installation was not configured, but did not explain the actual problem. Now it correctly detects and reports the problem that caused the error. (EXTWPTOOLK-636)

So, at now you get an actual error which block the cloning process. Could you please check ability to connect to database of your source WordPress manually with credentials, specified in wp-config.php?

Yes I can connect to my database using wp-config database username and password.

ssh.jpg

database.jpg
 
So, database of your WordPress located on local MySQL server (database server, where Plesk database located), with default port, that's right?

Probably, WordPress Toolkit unable to parse wp.config.php and extract database user name or database password incorrectly... could you please send me (privately, if it is more convenient for you) part of your wp-config.php where database access options specified? Then we can assess could it be parsed or not.
 
Back
Top