Search results

Can you locate the core file, and create a detail stack backtrace with GDB? If you feel difficult, can you send a temp root access to us, our staff can login and collect debug information.

This might work with current release. <FilesMatch "\.combined\.css$"> Options +Includes ForceType application/x-httpd-shtml </FilesMatch>

litespeed.com is another company, just use our domain name.

Or, PM/email us tmp root access to your server, so we can check the core file directly on your server.

We will have it addressed in our next release 4.2.2 .

Just remember that your modification could be overwritten next time you update configuration of SSL from web console. You can try the latest build 4.2.1, it should give RC4 priority when you configure SSL from web web console. /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1

It is normal that you encounter problem due to varies resource limits applied by WHM, even cPanel itself instructs you to run easyapache from command line if problem with the web console interface. Since you can do it from command line successfully, we believe it is the way how it works, no...

understood. First thing you can try is to switch back to Apache temporarily see if you get the same result, if yes, it is not LiteSpeed bug, but a configuration issue. If no, you can turn on debug logging of LSWS, then remove error_log file, restart LSWS, make a request to the problem domain...

Need to login and take a look. Could be something special in Apache server configuration. Can you PM or email temp root access to bug@litespeed... .

Please check if any core file under /tmp/lshttpd and /tmp/lshttpd/bak_core . send us the log file. Upgrade to the latest 4.2.1 build with /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1 if it does not help, send us a temp root access, we will investigate on your server if you want.

Maybe index override in .htaccess was disabled. Try switching back to Apache temporarily, see if you get the same result.

Please try the latest 4.2.1 build. /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1

It is a global option. When X-Forwarded-For header is not available, LiteSpeed still use REMOTE_ADDR. For security reason, LSWS only use X-Forwarded-For IP if REMOTE_ADDR is a TRUSTED IP listed in ACL, so, it should be safe to enable X-Forwarded-For globally.

Likely due to memory limit applied by WHM/cpanel when run the script from the interface.

No, that directive is not supported yet, please use AddOutputFilter AddType AddHandler SetHandler instead.

How about downgrade LSAPI to 5.5 for the 4.1.13 box? The php-litespeed package is still there, just change the version number in the download link, then locate the existing PHP build directory, replace *.c and *.h under sapi/litespeed directory, run 'make' again to build the PHP binary. If you...

Can you switch back to 4.1.13 and see if you get 503 errors as well? I have noticed on one customer's server using cloudlinux, that lsphp5 processes was killed by signal 9, which causes 503 errors, not sure who send signal 9. I wonder if it is caused by cloudlinux update or not.

It will be available with LSLB 2.0 release, which adds generic Layer4 load balancing. Current LSLB is a Layer7 load balancing, does not support MySQL.

It works fine in our cPanel test environment. Can you verify whether it works properly under Apache by switching back to Apache temporarily? Just in case it is a configuration error. If it works under apache, we will investigate.

Thank you for your feedback. We understand your points. We do not follow that route because it will really slow us down with bug fixes. We want to be stay agile/swift/efficient with bug fixes, and push bug fixes as soon as possible. We do have internal testing and beta user testing, but in real...