WordPress ToolKit task fails: WP-CLI command has not finished working in 60 seconds, so it was terminated

Symptoms

• WordPress Toolkit cloning task fails with the following error message:

  PLESK_ERROR: WP-CLI command has not finished working in 60 seconds, so it was terminated. Usually this means that there are problems with WordPress installation itself, for example it could be infected with malware. Check the wp-config.php file of the installation for potential malware code.

  or the following message is received via email:

  PLESK_INFO: WordPress Toolkit was not able to finish running an operation on this site in 60 seconds, so the operation was terminated. This could mean that your WordPress installation might be infected with malware. Check the wp-config.php file of the installation for potential malware code or run an anti-virus scan. If you cannot find any traces of malware, try running the operation again later.

Cause

WordPress Toolkit has a default timeout of 60 seconds to skip suspicious/infected WordPress instances, but this value is not enough for the affected instance. Probably, this is caused because the WordPress Toolkit cannot finish the cloning task due to an insufficient amount of CPU and RAM resources available or there are many files to be copied to the new staging instance.

Resolution

Increase WordPress Toolkit default timeout value:

1. Log in to Plesk GUI.

2. Install the extension Panel.ini Editor.

3. Go to Extensions > My Extensions > Panel.ini Editor > Open > Editor.

4. Add the following lines to the end of the text field and click Save:

   CONFIG_TEXT: [ext-wp-toolkit]
   wpCliTimeoutHeavy = 1800
   wpCliTimeoutMedium = 300
   wpCliTimeoutRegular = 300
   wpCliTimeoutRegularTimeout = 180
   wpCliTimeoutMaintenanceTimeout = 180

In case the issue persists, scan and remove malware from the WordPress instance with an antivirus software.

Additional Information

Wordpress Toolkit Cloning hangs or stops after 60 seconds