XCloner

I’ve posted the quick fix in the new 4.1.3 version, thank you for the fast response, it seems to work fine now.

Can you detail if you do a full backup restore or only the wp-content/ folder?

You could also try and download the backup archive locally , extract the theme files and upload as needed.

You need to check your site error log, you should get some more details on the 500 error there.

If the backend is still active, please check the logs from xcloner backend as well, you might see the exact error there also.

If you manage to fix that, the restore process steps are detailed in the xcloner backend, restore page. The xcloner_restore.php script url needs to be pasted there as that’s the restore API end point.

The cli cron command should be in the format

php /path/to/cloner.cron.php

Meaning it uses the php executable to trigger the action.

The backup process is probably timing out, i suggest changing the cron command to CLI.

This type of error is not generally thrown by XCloner, it could be a conflict with another plugin, it might be worth disabling each plugin one by one and checking if that message stops appearing.

Looks like a database connection issue, can you paste the lines before it to see what might this relate to?

Can you please confirm which webdav service are you using? Do you have any errors from your webdav server?

Hi Tobias, have you tried setting up a cron scheduler through the server using the php CLI command? That usually helps with the upload timeouts. And yes, increasing the max execution time would help, but there are also server side parameters which you need to check with your hosting support to ser if they can be adjusted.

No, that is not an error… are you able to debug the XHR request using the browser inspector?

Are XCloner logs enabled?

Server logs would help, but please check also the XCloner logger from it’s dashboard, you might find something there also

You might need to debug the server response of that ajax call, it might be that instead of json, the server is sending some other type of data which breaks the structure. Do you have the same issue for automated backups?

It might be an issue with the webdav library and I will try to update it in the next release.

Are you able to test with another webdav service to see if you get the same error?

Please also indicated which php version are you using.

Thanks

You could use xcloner to automatically transfer the backup to failover target, however automatic restore would require a custom script to be created, one which will extract the archive files and then import the database and update the wordpress config settings where needed.