Search results

Not everything can be done in this way, please check our wiki for related topic regarding what you want to do.

Usually, it need to be done through .htaccess or virtual host configuration customization through cPanel vhost level include file.

Updated, please try again.

Please try /usr/local/lsws/admin/misc/lsup.sh -d -f -v 5.1RC3 the file-inspect.pl should run as the user that lshttpd worker process running as.

A graceful restart of LSWS will reset the Uptime. That's normal.

What will you get if you run the same rule under Apache mod_security? Audit log only follow the rule actions. It looks alright to me. Maybe it missing some environment variable or parameter when run file-inspect.pl through the engine. Or, there is permission problem. file-inspect.pl run as...

There is no issue. those log messages are for INFORMATION only. If you do want to see those messages, just change log level to NOTICE or WARNING as NiteWave instructed.

"Debug Level" should be set to "NONE", only set it to other value when you need to see the debug level logging. Log level can be set to "DEBUG" or "INFO".

1.4.14 has been released, you can give it a try.

If you use native LSWS vhost, not through Apache configuration, you need to set https://www.litespeedtech.com/docs/webserver/config/reqfilter#censorLogLevel It is equivalent to "SecDebugLogLevel", ModSec debugging log is logged as "INFO" level in error.log, so your Litespeed server log level...

if you want check if a rule was hit, you should setup audit log. LiteSpeed does not scan a request results in 404, or a request to static asset.

if you use it with control panel, just change Apache mod_security configuration SecDebugLogLevel 9 the debug logging is in the error log.

Please try purging LiteMage cache, it should trigger built-in crawler to start crawling. If it does not populate the URL list, something is wrong.

Have you running it in production? or staging? Need more feed backs on stability of 5.1RC2 release.

Please try 5.0.9. should be fixed. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.9

So, there is a dedicate SSL certificate for https://whm.testdomain.com? What is the certificate actually being used? The self signed default certificate created by cPanel? We may need to check the server with temp root access to find out the root cause. If you would like, please contact...

Looks like LiteMage is not enabled for that account. Make sure you account level litemage configuration is correct. If you configured litemage with cache root /home/user/litemage_cache, you may need to create the cache root directory, and make it writeable by nobody user, otherwise there might...

Make sure you are not running out of disk space. can you please remove the whole litemage_cache folder instead of removing files under litemage_cache folder. then restart LSWS, see if it works or not.

Please try change your configuration to Name: yap address: 192.168.1.200:80 notes: not set max connections: 100 connection keep-alive timeout: 20 environment: not set initial req timeout: 100 retry timeout: 1 response buffering: no turn on server debug logging, send us the full debug log of the...

We have fixed this internally, the change involved is pretty big, please wait for 1.4.14.