How do I deal with a failed clone/restore process?
When you try to restore the site that is not properly connected with your ManageWP dashboard, you might get the following message:
We had trouble restoring the website. Please configure FTP settings and try again. Error message we received: We were unable to set up the cloner script via ManageWP Worker. Error: ManageWP is having trouble connecting to your website. Please make sure your website is online with the ManageWP Worker plugin active. If you are still experiencing this issue please contact us.
We are not able to communicate with the Worker plugin in order to restore the site. You could resolve this by adding the FTP credentials under Backup Settings > FTP Settings. That way, we will have FTP access and the restore process should be able to finish correctly.
When the destination site is added to ManageWP dashboard, and this cloning type is used, you might see the following error:
Server error: `POST http://lexample.com/cloner.php` resulted in a `500 Internal Server Error`
This usually means that the destination website is not properly connected with ManageWP dashboard. In this case, you might choose New website as a cloning option, and enter FTP and Database credentials there in order for cloning process to work.
Failed to flush rewrite rules: Client error: `POST http://example.com/cloner.php` resulted in a `403 Forbidden`
This message usually appears if the permissions are not set to 755 (for folders) and 644 (for files) on the destination website.
In order to resolve this, you might follow the instructions from this link.
Client error: `POST https://dev.stephanwelzandco.co.za/cloner.php` resulted in a `404 Not Found`
This might happen if our IP addresses are not whitelisted on the destination site, and you could resolve the issue by whitelisting the addresses from the list here.
Also, it is possible that other than index.php file, all other files are not accessible from the web. In order to test this, you might upload a test.txt file to the destination server (WordPress installation folder), and try to access it from your browser by typing example.com/test.txt (instead of example.com, you should type the destination URL) .
Failed to restore the tables. The action \"pdo_restore_tables\" failed: SQLSTATE[42000]: Syntax error or access violation: 1115 Unknown character set: 'utf8mb4'
In this case, you might check if the database user that you provided has all previlleges. Also, checking if the character set is correct and if MySQL version is 5.6 or greater might help with this.
SQLSTATE[28000] [1045] Access denied for user 'database_exampleuser'@'localhost' (using password: YES)
This message indicates that provided database password might be incorrect, and you could check wp-config.php file in order to find the correct credentials.
The credentials should look like this:
/** The name of the database for WordPress */
define(‘DB_NAME’, ‘database_example’);
/** MySQL database username */
define(‘DB_USER’, ‘database_exampleuser’);
/** MySQL database password */
define(‘DB_PASSWORD’, ‘examplepassword’);
/** MySQL hostname */
define(‘DB_HOST’, ‘localhost’);
You might try the cloning process by using the database credentials from wp-config.php file, and it should finish successfully.
We got HTTP error 404 after attempting to visit the connection test file that we uploaded. Please, double-check the provided FTP path. If you are certain that the path is correct, please make sure that PHP files other than /index.php can be accessed from the web.
The FTP path should lead to the the WordPress installation folder. If the folder is not created yet, the cloning process could not create the path, and you should set everything before trying the cloning process again.
If the FTP path is correct, it is possible that, other than index.php file, files are not accessible from the web, and you might test this by following the steps above.
We were unable to finish the clone process due to an error produced by WordPress on the destination website. Please check if plugins on the website are compatible with PHP running on destination and try disabling the incompatible ones.
There are two ways to resolve this issue if you ever enconter the error message above.
First, you should check if the destination server is running on lower PHP version that the source. If that is the case, you may contact your hosting provider in order to upgrade the PHP version on the destination.
Sometimes it is not possible to do that, so you could deactivate the plugins that are incompatible, backup the source site after deactivating those plugins, and use that backup for the cloning process. That way, the cloning process should be successful.
Yes
No
