Forwarded to devs Wordpress "Clone this instance"

[NicolasP.]

TITLE:

Wordpress "Clone this instance"​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk Onyx 17.5.3 Update #14
Centos 7.3.1611 (Core)‬​

PROBLEM DESCRIPTION:

There is an issue when I am trying to clone Wordpress to another domain.

I am getting this error:

Copying database

• -- Connecting to localhost...
• mysqldump: Got error: 1045: "Access denied for user 'wordpress_g'@'127.0.0.1' (using password: YES)" when trying to connect

​

STEPS TO REPRODUCE:

Just go to a domain that uses Wordpress and click clone.

And follow the instructions.​

ACTUAL RESULT:

I found what causes this issue.

When the database user "Allow local connections only" is not allowed to use 127.0.0.1.

If you change it to "Allow remote connections from any host" it works
You must change it for current database user and for all database users from "Database Hosting Preferences" in Tools.​

EXPECTED RESULT:

I don't want my database users to allow remote connections.

And why Wordpress Clone needs remote connections enabled as it runs locally?​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

Thank you for report! Bug was confirmed and submitted as EXTWPTOOLK-806.
Developers informed me that it should be fixed in one of the nearest updates.

 

[NicolasP.]

Thank you for report! Bug was confirmed and submitted as EXTWPTOOLK-806.
Developers informed me that it should be fixed in one of the nearest updates.

Brilliant Igor.

Clone Instance is an excellent tool for those who use Wordpress.

Thank you

 

[Daniel Slyman]

Here's the solution which worked for me:
WordPress cloning issue: Access denied for user 'admin_wordpress_user'@'127.0.0.1' (using password: YES)

PLEASE NOTE:
I had to allow a connection from 127.0.0.1 for both the user of the original WordPress instance and the cloned one. The cloned user only becomes known after one failed attempt, it will be displayed in the error message.

Any update on a permanent fix for this? I came to rely on this for my work.


ADDITION:
If you are anything like me and use this extension quite frequently, you can also allow remote connections from 127.0.0.1 globally in the Database Hosting Settings. This way you won't need to do this for any of the database users themselves. At least this worked for me and will save me time until the bug is fixed.

Plesk > Tools & Settings > Database Hosting Setting

[Plesk] /admin/database/settings/