Search results

  1. M

    [Resolved] LiteSpeed not returning Content-Encoding header for Range requests, breaks gzip

    Please try the latest 4.2.19 build, we fixed a gzip related issue yesterday. If it does not fix it, we may need to login and take a look at it.
  2. M

    FastCGI .fcgi Internal server error Django documentation incomplete

    just try that again if running from command line does not give any error about django.core .
  3. M

    Failed to bring up LiteSpeed - Plugin Cpanel

    Have you used trial license on that server? maybe your trial period has been used up? please contact us through our ticket system.
  4. M

    Multiple SSL configuration

    so, it is a configuration issue, has been sorted?
  5. M

    FastCGI .fcgi Internal server error Django documentation incomplete

    /usr/local/apache/logs/stderr.log shows error related to django it also have error for fastcgi The django setup is wrong.
  6. M

    FastCGI .fcgi Internal server error Django documentation incomplete

    Your application is talking FCGI protocol, it wont work with lswsgi, which talks in LSAPI protocol. You have to update the code to use WSGI interface.
  7. M

    Multiple SSL configuration

    Make sure the listener to vhost mapping uses the correct domain name, in you case, you must use "example2.com", cannot use "*" to map to example2.com .
  8. M

    JS files were not compressed when compressing through Gzip

    Please force reinstall 4.2.18 with command /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.18 if problem persists, please let us know how to check the problem.
  9. M

    FastCGI .fcgi Internal server error Django documentation incomplete

    You cannot expect real fcgi to work with lswsgi, they speak in different protocol, if it is pure wsgi application, it will work if you rename the file from wsgi to fcgi. Have you tried the sample hello world wsgi code? rename it to fcgi?
  10. M

    Could not compile APC extension

    5.4.xx is your safe bet.
  11. M

    Could not compile APC extension

    apc is not compatible with PHP 5.6, you should use opcache, xcache.
  12. M

    Problem with variables

    Please upgrade to the latest build of 4.2.18 /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.18 should be fixed.
  13. M

    litespeed showing internel server error

    Just uninstall LSWS from WHM plugin, remove everything, then reinstall from scratch.
  14. M

    litespeed showing internel server error

    Is the partition full?
  15. M

    A setenv question

    wont work with 4.2, it is on the to-do list of 5.0.
  16. M

    A setenv question

    SetEnv is upported in 4.2 already, your app may work just fine with 4.2 . If any problem, just show us the SetEnv directives used, we will see whether it should be supported in 4.2 or not. We hope we can release 5.0 by the end of this year. The 5.0RC is getting ready for production uses.
  17. M

    Prevent Litespeed from blocking Varnish

    You can turn it off completely http://www.litespeedtech.com/docs/webserver/config/security#blockBadReq
  18. M

    [Resolved] HttpConnection::sendHttpError __assert_fail () from /lib/i686/cmov/libc.so.6

    latest build of 4.2.18 will log a warning message instead of abort(). Just do a force update with /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.18
  19. M

    [Resolved] HttpConnection::sendHttpError __assert_fail () from /lib/i686/cmov/libc.so.6

    Looks like the "ErrorDocument 404 " URL is longer than 2KB, check the core file with gdb, do command up 4 print *pErrDoc print *this to find out more information about the bad configuration, then fix it.
  20. M

    Litespeed & A2Billing 404 Error

    There should be a rewrite rule in .htaccess to rewrite the URL to a PHP script.
Top