Search results

You can turn on debug logging for a while if you have to find out which vhost.

what configserver exploit? any correlation with LSLB? It is recommended to test it in your staging server first.

please remove /usr/local/lsws/autoupdate/platform, then try again.

remove the directory, not the configuration.

remove cache store path.

Please check /usr/local/apache/logs/error_log, it should show the reason why. One possibility is PHP script handler is not setup properly, like a custom PHP handler does not exists for MIME type application/x-httpd-php55.

HTTP/2 will not interfere with Atomic WAF. It is not recommended to use proxy mode with litespeed, which put Apache as a front-end proxy server, it will slow down your server.

The best way is to let us login to the server with temp root access to figure out what happened. If you prefer not to giving temp root access, you can turn on full debug logging, then send us the error log.

Yes, if you use a SSL from a vendor.

It should have -----BEGIN RSA PRIVATE KEY----- There should be two files generated when you create the CSR request, one is the private key file, you never send private key file to anyone. The certificate signed by SSL vendor should have -----BEGIN CERTIFICATE-----

Are you using cPanel? We tested in our cPanel test box, autoindex works fine with 5.0.7 . Please make sure you get the latest build of 5.0.7, /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.7 If you still experiencing the problem, we may need to login to check related Apache configuration.

Please force reinstall 5.0.7 to get the latest build. The content-length header should be added for the HEAD request.

Yes. If you use cPanel, you should customize the per-vhost include file.

You have to put it inside the real <VirtualHost> configuration section.

It will be supported in our up-coming 1.4.12 release. Sorry for the confusion, we finished coding a while ago but have not release it yet. Will be release in this week.

No, cannot change audit log configuration at vhost level. the best you can do is to add that rule only to a virtual host.

You can use "SecAuditLogParts" to change it.

LiteSpeed does not log POST payload in error log, you can use audit log part "C" to log request body.

Yes, you can compile your own PHP binary, Or, you can use ready to use RPM packages. REMI or our own repository. https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:rpm

5.1RC1 has been released. @rbl and @inspectFile support has been added. Have been testing @rbl in production for a few days to find forum spam. looks like it is working well. Due to the big internal changes, we release it as release candidate, user need to be careful with rolling out. It is...