Search results

We are going to have a major change in our configuration file, which will use JSON format instead of XML. by that time, include configuration files will be supported. Maybe in a month or two.

<LocatioonMatch> must be in the main configuration file. does not work in .htaccess, same with Apache as designed.

It has nothing to do with the 500 error, you need to set "Debug level" to "HIGH", then try the URL produce 500 error. grep error log with the IP that the request originated.

Fix is in 4.2.8 release.

no. litespeed static linked with official openSSL lib.

what exactly is your problem?

If the patch get into the official OpenSSL release, we will use it.

upgraded our cPanel test server to MySQL 5.6, then build matching PHP, the default lsphp5 binary has been updated to using MySQL 5.6.15 Client API. CloudLinux also has alt-php RPM for MySQL 5.6. The PHP binary compiled with cPanel easyApache does not use mysqlnd, The matching lsphp5 does not...

Build Matching PHP will update default lsphp5 binary after you run easyApache. If you use PHP selector, the binary is from RPM provided by CloudLinux. you need to contact CloudLinux about that.

LiteSpeed SSL always follow server's preference.

You may need to turn on debug logging, then reproduce the problem. then locate log entries related to this request with your IP.

Please check /usr/local/apache/logs/error_log if you are using cPanel, otherwise, check /usr/local/lsws/logs/error.log .

same as with 4.x release, install gdb, set server Administrator's email. the crash report will be sent to that email. forward crash report to bug@litespeed....

We will check and have it fixed in RC2 release.

LS wont change configuration by itself. you should check file time stamp and admin console access log. Resouce limit is part of LVE, not CageFS, I guess you need to look into what and why resource limit has been reached.

There could be rewrite rule compatibility issue. What you can is to turn on rewrite log for that vhost, just add RewriteLogLevel 9 to in <VirtualHost ...> </VirtualHost> temporarily, restart server, then check rewrite related log entries in the error.log. Post your rewrite rule may help...

Please turn on debug logging, restart LSWS, access the site, check /usr/local/apache/logs/error_log if using cPanel, if not, check /usr/local/lsws/logs/error.log, it should have something about loading .htaccess, and process each directive in the log.

just remove the ENV LSAPI_ALLOW_CORE_DUMP=0 completely. The crash will be logged, but "core dump: 0" indicates there is no core dump file generated. the log message cannot be turned off.

%{SERVER_NAME} is an internal variable using vhost ServerName. In your case, if you expect "Host" header, you should use "%{HTTP_HOST}"

Maybe HTTP_USER_AGENT env was modified by a rewrite rule or something, LiteSpeed itself does not do post-processing of "User-Agent" header.