Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
Thanks! It was indeed caused by a caching plugin. Unfortunately, I wasn't aware that I should be editing (duplicating for the original first) the wp-config.php file before doing any cloning.
@Kaspar there is no domain > databases section on my end or maybe I'm just too dumb to find it. But if I click a specific domain, and click databases, I get this which is also not like yours.
Is there anyway to salvage this? Unfortunately, I need this clone to work as-is so I'll have to make do with manually editing files or something.
I've clicked the `Update Site URL` a hundred times, updated the relevant wp-config.php and rows in *_options table but still no luck.
Any ideas...
Hi! How do I change the db attached to my domain so that it's the same as the one indicated in my Wordpress site? I already tried changing on Wordpress end and it seems the wrong way.
I deleted the subdomain site and redid the clone and now it goes the other way around. The wp-login.php scripts and assets of the subdomain site point to the tld site so that when I login, it makes the POST request to the tld site. Is this acceptable/expected behavior of `clone`? Should we just...
Cloned our site from le***ss.com to italia.le***ss.com using WP toolkit clone and now when I try to login to the wp-login of the tld site it instead makes a POST to the subdomain and even all the assets point to the subdomain site. Also, when I look at the wp toolkit index there's now 2 entries...