archprime

OK, more poking around revealed that the wp.config file had been set to disable wp_cron (possibly by the hosting company?). I tried reenabling it (per below), and this time was able to get a scheduled backup to actually occur – though I was logged in to Xcloner website at the time, so presumably the presence of human activity was triggering wp_cron to work?

/** Disable the WP_CRON processes*/
define('DISABLE_WP_CRON', false);

How should scheduled backups be initiated – via the wp_cron setting within the Xcloner wordpress installation (which would normally never be visited by a user), or via an external recurring cron task set up with the host?

• This reply was modified 1 year, 1 month ago by archprime.

I am seeing this when I try to create a new backup

'{"readyState":4,"responseText":"Error 406 - Not Acceptable
Error 406 - Not Acceptable
Generally a 406 error is caused because a request has been blocked by Mod Security. If you believe that your request has been blocked by mistake please contact the web site owner.
","status":406,"statusText":"error"}'

Does Xcloner require that sites it backs up are not protected by Mod Security? Otherwise how do I safely avoid getting this error?

I contacted my webhost, who advises the Mod Security rules are the same for most shared hosts, and get regularly updated. They suggested it would be a bad idea to disable mod security, and that I need to contact you to request the plugin be updated for better compliance with latest standards.

• This reply was modified 1 year, 1 month ago by archprime.
• This reply was modified 1 year, 1 month ago by archprime.
• This reply was modified 1 year, 1 month ago by archprime. Reason: include further information

Apologies, rather than hanging around to troubleshoot, I just recreated all the schedule items. One thing I found the original schedule items had in common was outdated database references (WordPress installations were shifted to another account/server with the hosting company).

What also seemed to help was disabling Modsecurity (I had been getting frequent error 406 when trying to undertake Xcloner admin tasks too soon after a backup was done, or too often in succession, and sftp file transfers had been failing randomly – all seemed to go away with mod security turned off).

How important is having Mod_security enabled for Xcloner?

Perhaps this belongs in a separate post, but a few other things related to scheduling were noted:

Although a first backup has been completed for every WordPress installation in the schedule, the schedule does not reflect this, with all ‘last backup’ entries remaining blank, despite having ‘executed’ status.

Each ‘executed’ status notification is a hyperlink, but it links to nothing

There is also no obvious or simple way to manually initiate a one off backup from a schedule item as you would intuitively expect, at least not without changing the schedule start time to the current date, which then offsets the scheduled recurrences in ways that may not be intended.

This forces a user to otherwise define a new backup – with all the risks involved in that (wrong database selection, wrong file exclusions etc). This seems crazy when a perfectly good backup definition already exists.

It seems all I can do is delete an existing schedule item and create a new on by the same name

Hi, I found the below logs under the Xcloner Debugger Tab – does this help? There are no recent error logs on the server.

[2023-02-20 13:48:27] php_system.DEBUG: E_DEPRECATED: array ( 'type' => 8192, 'message' => 'Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice', 'file' => '/home/primen9/public_html/xcloner/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php', 'line' => 91, ) [] []
[2023-02-20 13:48:12] xcloner_file_system.DEBUG: Estimating file system reading time [] []
[2023-02-20 13:48:12] xcloner_file_system.INFO: Cleaning the backup storage LOCAL on matching rules [] []
[2023-02-20 13:31:15] php_system.DEBUG: E_DEPRECATED: array ( 'type' => 8192, 'message' => 'Implicit conversion from float 804238.7962341309 to int loses precision', 'file' => '/home/primen9/public_html/xcloner/wp-content/plugins/xcloner-google-drive/vendor/phpseclib/phpseclib/phpseclib/Net/SSH2.php', 'line' => 1209, ) [] []
[2023-02-20 13:31:13] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 13:31:13] xcloner_remote_storage.INFO: Checking validity of the remote storage SFTP filesystem [] []
[2023-02-20 13:31:13] xcloner_remote_storage.DEBUG: Saving the storage SFTP options [] []
[2023-02-20 13:30:58] php_system.DEBUG: E_DEPRECATED: array ( 'type' => 8192, 'message' => 'Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice', 'file' => '/home/primen9/public_html/xcloner/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php', 'line' => 91, ) [] []
[2023-02-20 12:43:50] xcloner_remote_storage.INFO: Creating the Google Drive remote storage connection [""] []
[2023-02-20 12:43:48] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:43:48] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:43:48] xcloner_remote_storage.INFO: Creating the FTP remote storage connection [] []
[2023-02-20 12:42:42] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:42:42] xcloner_remote_storage.INFO: Checking validity of the remote storage SFTP filesystem [] []
[2023-02-20 12:36:13] xcloner_remote_storage.INFO: Creating the Google Drive remote storage connection [""] []
[2023-02-20 12:36:10] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:36:10] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:36:10] xcloner_remote_storage.INFO: Creating the FTP remote storage connection [] []
[2023-02-20 12:28:09] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:28:09] xcloner_remote_storage.INFO: Checking validity of the remote storage SFTP filesystem [] []
[2023-02-20 12:27:58] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:27:58] xcloner_remote_storage.INFO: Checking validity of the remote storage SFTP filesystem [] []
[2023-02-20 12:22:33] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:22:33] xcloner_remote_storage.INFO: Checking validity of the remote storage SFTP filesystem [] []
[2023-02-20 12:21:55] xcloner_remote_storage.INFO: Creating the SFTP remote storage connection [] []
[2023-02-20 12:21:55] xcloner_remote_storage.INFO: Checking validity of the remote storage SFTP filesystem [] []

• This reply was modified 3 years, 3 months ago by archprime.

Hi thanks for your reply. Yes I had worked through that, and application is registered, and I have been supplied the ID and secret from Microsoft – but when using these in Xcloner, Xcloner gives connection error