Search results

it is compatible with LSWS 5.1, support for mod_security @fileinspect operator has been added.

not any more.

I think it because that IP has used trial before. Need to have that IP cleared from our trial tracking DB, or use a production license key.

This feature is not available yet. we may add that in the near future.

Yes you can use different cache folder for each vhost. Just use the the vhost level include file to set that.

There is something that cause 5.1.4 to crash, maybe you send us temp root access to bug@litespeed..., so we can investigate.

Add vhost include file, then add

those rules are not supported by 5.0.x, some of them are supported by 5.1, so, you can try 5.1.4 with /usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.4

maybe your IP need to be cleared from trial tracking DB. Please contact sales@litespeed...

that will stop xenforo cache from working as well. assuming more traffic to xenforo, better just uninstall wp cache plugin, and use xenforo plugin.

We found that it is caused by a conflict of the same lscache cookie used for both xenforo and wordpress plugins. You will have this problem when both plugin are enabled, we will try to fix it later. For now, you can use one plugin without problem, if you do not care too much about the login...

The best way to have it fix is let us to login to the server to check the drupal site to figure out why cache is triggered. Please contact bug@litespeed Our goal is to make lscache working well in shared hosting environment.

Please try updated 5.0.14, a related bug has been fixed. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.14

Can you please try download the package again, both 5.1.4 and 5.0.14 packages are good to me.

when set Check Public Cache - Yes LiteSpeed cache may cache a page, if it claims to be public cacheable in the response header. Or, that customer is playing with LiteSpeed cache control with rewrite rule.

which package? make sure you use the correct one for your OS. All 5.1.4 package looks good to me.

Please make sure you are using 5.0.14+

no idea, if it happen again, just restart Litespeed with debug logging enabled.

you need to turn on mod_security debug logging by changing debug level configuration to SecDebugLogLevel 9

We will update openssl lib with next build. We have SSLv2 disabled long time ago, as long as the SSL certificate is not shared, your server is not vulnerable.