Can anyone advise me about an apparent "well-known" issue of a problem for those using Litespeed Webserver and LSCache Plugin, whereby scheduled backups have a problem. in our own experience, the local backup works ok, but when you want to have a copy sent across to a remote location (in our case Dropbox), there is a failure due to taking too long and it falls over. Here is an excerpt of an advice page we were linked to from the popular plugin UpdraftPlus;
I am having trouble backing up, and my web hosting company uses the LiteSpeed webserver
LiteSpeed appears to have problems with all WordPress scheduled tasks that last more than a very short time – including all backup plugins. Adding this in an early position in the
Adding the above line will make the LiteSpeed warning on UpdraftPlus’s settings page go away – this does not mean that the problem is definitely fixed; you will only know that via testing. If the above does not help, then you can try this: use WordPress’s alternative scheduling system – instructions here. The instructions amount to one thing: add a line to your
If that does not help you, then you’ll need the help of your web hosting company to see why WordPress’s scheduler isn’t working on their setup, or is terminating it prematurely. Or failing that, you’ll need a different web hosting company. This problem is a generic one affecting all backup plugins on WordPress that run via the scheduler (which is all of them, as far as we know).
I would welcome any advice from anyone familiar with this issue.
Regards
Craig
I am having trouble backing up, and my web hosting company uses the LiteSpeed webserver
LiteSpeed appears to have problems with all WordPress scheduled tasks that last more than a very short time – including all backup plugins. Adding this in an early position in the
.htaccess file in your WordPress root folder may fix the problem:RewriteRule .* - [E=noabort:1]Adding the above line will make the LiteSpeed warning on UpdraftPlus’s settings page go away – this does not mean that the problem is definitely fixed; you will only know that via testing. If the above does not help, then you can try this: use WordPress’s alternative scheduling system – instructions here. The instructions amount to one thing: add a line to your
wp-config.php file as follows:define('ALTERNATE_WP_CRON', true);If that does not help you, then you’ll need the help of your web hosting company to see why WordPress’s scheduler isn’t working on their setup, or is terminating it prematurely. Or failing that, you’ll need a different web hosting company. This problem is a generic one affecting all backup plugins on WordPress that run via the scheduler (which is all of them, as far as we know).
I would welcome any advice from anyone familiar with this issue.
Regards
Craig
Last edited by a moderator: