Search results

great! please check if this issue still exist. if there is a new post, homepage should update automatically (by default). you can configure it through the plugin: LiteSpeed Cache Settings Purge Rules Front page: by default it's checked.

not good to set cache root here, because lsws itself are installed under this folder. please try to set it to /home/lscache or /tmp/lscache etc, and see if the issue still exists.

Sorry for the result. one of main targets is to make lscache and lscache wordpress plugin easy to use, but apparently failed on your case. in most cases it just works without problem. if you provide ssh root access to the server, I'd take a look where the problem might be. since we've been...

if you install lscache for wordpress plugin, following rewrite rules should not be needed: and should keep CacheLookup public on in your .htaccess

right. then maybe lscache root not set or not set correctly. what's the current lscache root and its user/group/permission ?

no "X-LiteSpeed-Cache: hit" in it, so this page is not cached. if "X-LiteSpeed-Cache: hit" not seen in any page, then lscache is not set up correctly somewhere. please try: add <IfModule LiteSpeed> CacheLookup public on </IfModule> in .htaccess in wordpress root, see if it'll fix it,

I did unit test on litespeed version is 5.0.19(Build 5), there is no problem found -- lsws can handle it well. how about you create an empty file /home/bursatum/public_html/403.shtml, so in above log, 1st line will disappear. then see if 2nd line will appear still ?

if remove this line: SetEnvIfNoCase User-Agent from .htaccess, will 403 error be gone ?

can you post .htaccess here ?

disk space has no problem by your screenshot. I think this is the reason why all your websites suspend for a while -- lsws restart itself too frequently. this usually not happen, we need trace why it has happened on your server. can you try:

weird issue. how about disk space status ? is it possible full ? #df -h #df -hi p.s. 5.0.18 has no such issue ? if not sure, can you switch back to 5.0.18 for a while ?

this is ok to be ignored. what's the os version ? Redhat/CentOS 7.x ? can you fore update 5.0.19 again to see if the issue still exists ? #/usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.19

please wait for some time, our expert will answer it after they come to office in EDT timezone.

yes, AFAIK, that's the mechanism, use ESI to support WooCommerce just like litemage. it's already taken care of for current lscache plugin for wordpress ( search woocommerce in https://www.litespeedtech.com/solutions/wordpress-acceleration/litespeed-cache/release-log) our developer should be...

I confirmed the solution as well. #curl -I http://localhost:7080/status?rpt=summary HTTP/1.1 401 Unauthorized #curl -I http://username:password@localhost:7080/status?rpt=summary HTTP/1.1 200 OK username / password need put into /usr/local/lsws/admin/htpasswds/status 1) can have multiple...

is 1.2.3.4 followed by a trailing T? i.e., 1.2.3.4T instead of 1.2.3.4 don't remove ALL

latest version ( now 5.0.19) can handle some cases automatically without any manual work. if you have found any issue (still need some manual change than apache), please post here.

that's an old post. please update to latest 5.0.19, see if the issue still there. if we can confirm it, will fix it.

"Configure Parameters" is at "Step 2 : Choose PHP 5.6.24 Build Options" what's your current options(parameters) ? I suggest to try minimal option first -- the minimal one is ""--with-litespeed" only.

suggestion: 1) upgrade to 5.0.19, then you can build latest 5.6.24 instead of 5.6.23 2) in "Configure Parameters", leave only "--with-litespeed", see if build can complete 3) if 2) is ok, then build failure 's related to some "Configure Parameters", you can gradually adjust it, see which...