Turkey (Turkish)
Germany (German)
Worldwide (English)
Source siteWordPress health and WP-CLI
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
WP Toolkit combines cloning and Smart Update operations into file copying, temporary database user, search-replace, WordPress health check, and screenshot tests. It may stop due to disk space, WP-CLI timeout, malware, trigger DEFINER, or target collision issues.
WP-CLI command has not finished working in 60 seconds
WP Toolkit was not able to finish an operation in 1800 seconds
Unable to import database
The user specified as a definer does not exist
WordPress instance is brokenCloning is not just file copying. WP Toolkit creates the target domain and database, transfers the source data, changes URLs, and verifies that WordPress is working. Smart Update also tests the update on the temporary clone.
60 second WP-CLI timeout indicates the command did not complete within the expected time. Malware, corrupted wp-config.php, heavy plugins or external connection wait may be the cause.
The 1800 second general operation timeout may occur due to a large media index, slow disk, resource limit, or stuck database import.
Unable to import database and DEFINER error, the user definition in the trigger/view object may be incompatible with the temporary import user of WP Toolkit.
Smart Update does not replace backup. A separate Plesk backup must be taken before the update and sufficient disk space must be available for a full copy at the target.
Using force overwrite in the cloning target may irreversibly change the existing site files and database information. The target domain and path should not be used without being verified for empty spaces.
Search for the phrase you see in the email, browser, or SSH log. Each card includes meaning, probable cause, and safe initial action.
Meaning: The WP-CLI sub-process has not timed out.
Possible cause: Malware, corrupted config, slow PHP or external service.
Meaning: The general time limit for cloning or updating has been exceeded.
Possible cause: Large data, slow IO, stuck import or low resources.
Meaning: SQL dump cannot be applied to the target database.
Possible cause: DEFINER, SQL mode, package size, connection, or broken dump.
Meaning: Trigger/view is using missing MySQL user as definer.
Possible cause: User has been deleted or does not match the temporary import user.
Meaning: WP Toolkit cannot properly detect the WordPress core or its connection.
Possible cause: Missing wp-config, incorrect DB, fatal error, or file path.
Meaning: Old site URL or plugin redirect remains in the copy.
Possible cause: WP_HOME/WP_SITEURL, serialized data or cache.
Meaning: There is no area to create a full site copy for a test clone.
Possible cause: Large uploads, backups, or low disk reserve.
Meaning: Indicates that the target path or database contains existing content.
Possible cause: Incorrect target selection or old staging site.
No records matching this expression were found.
Commands are for root access. Collect only status and logs first; Do not change the permanent setting without seeing the reason.
plesk ext wp-toolkit --list -format jsonLists the WordPress instance ID and basic status in JSON on the server.
plesk ext wp-toolkit --info -instance-id 1Displays registration and status information for the specified WordPress instance.
plesk ext wp-toolkit --wp-cli -instance-id 1 -- core verify-checksumsWordPress compares core files with official checksums.
plesk ext wp-toolkit --wp-cli -instance-id 1 -- plugin listShows active plugins and versions in the context of WP Toolkit.
mysql -NBe "SELECT TRIGGER_SCHEMA,TRIGGER_NAME,DEFINER FROM information_schema.TRIGGERS WHERE TRIGGER_SCHEMA='wordpress_db';"The source WordPress lists trigger definers in the database.
du -sh /var/www/vhosts/example.com/httpdocs
df -h /var/www/vhosts/example.com/httpdocsCompare the file size required for the clone with the target filesystem free space.
plesk ext wp-toolkit --clear-wpt-cacheWP Toolkit clears the cache; does not delete the source site data.
Verify the source WordPress health, disk, target, database, and WP Toolkit process log separately.
Smart Update is not a backup. Back up your files and database using Plesk Backup Manager to a secure location.
Instance ID, wp-config, core checksum, and WP-CLI access are checked.
plesk ext wp-toolkit --info -instance-id 1Full clone requires more free space than source size and a free/safe target path.
If there is an import error, the first SQL error and DEFINER object are found; all triggers are not randomly deleted.
The subcommand that times out can be run via SSH to separate malware, external connections, or PHP limits.
The target site should not be pointed to the original domain; admin, cron, permalink, and payment/form flows should be tested.
WP-CLI timeout, suspicious code in wp-config and PHP handler compatibility are checked.
Trigger/view DEFINER, SQL mode, max_allowed_packet and dump error are examined.
WP_HOME, WP_SITEURL, cache, and redirect plugins are checked.
Dynamic content, cookie banner, cache and time-dependent components can create false positives; manual function test is performed.
A new clone should use a different subdomain/path or be intentionally cleaned after the target is fully backed up.
The WP-CLI command is not completed within the time limit. Malware, corrupted wp-config, PHP, or heavy plugin should be investigated.
The general cloning/ updating process has not been completed within 30 minutes. Disk IO, data size, and stuck sub-step are being examined.
Creates a test clone but does not replace the normal backup as per official Plesk documentation.
The first SQL error must be found; especially, DEFINER and target user permissions for triggers/views should be checked.
wp-config settings, WordPress option values, serialized data, cache or redirect plugin is possibly keeping the old URL.
You can modify the existing file and WordPress data on the target. However, only verified backups and the correct target should be used.
--clear-wpt-cache Clears WP Toolkit's own cache; WordPress cache plugin data is different.
By analyzing cPanel, WHM, CloudLinux, LiteSpeed, MariaDB, Exim and security layers together, we fix the root cause of the failure instead of just removing the service.