Search results

  1. M

    [solved] ssi echo encoding

    that's indeed a bug in SSI processing. Please upgrade to the latest 4.2.1 build: /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1
  2. M

    LSAPI and Shared Hosting not working

    Looks like there is no enough information for litespeed to detect the version of Rails being used, and it defaults to Rails 2.3 branch of code. If the Rails app involved is >2.3 release, you should set "RAILS_GEM_VERSION" variable in "config/environment.rb" explicitly for that application.
  3. M

    LSAPI and Shared Hosting not working

    change that line to
  4. M

    500 internal server , Cgi website

    Is it CGI? You need to strace the cgi process to find out what happened. It may not send back CGI response header at all.
  5. M

    Client IP in Header

    you need to ask your anti-ddos provider to send X-Forwarded-For header.
  6. M

    Symlink problem in 4.2

    you need to check /usr/local/apache/logs/error_log to find out the reason why it is denied, then adjust configuration accordingly. Try "Force reinstall" of 4.2, it might be fixed as we have adjusted default values to off.
  7. M

    FollowSymLinks in .htaccess

    There are many options, http://www.litespeedtech.com/docs/webserver/config/security/#forceStrictOwnership with 4.2, you can use "DisableSymlinkOverride On" in httpd.conf. or "VhostRestrained On" in httpd.conf
  8. M

    Symlink problem in 4.2

    It is just "On", "Off". Also, check http://www.litespeedtech.com/docs/webserver/config/security/#forceStrictOwnership
  9. M

    LSWS 4.2.0 Bug - No .rtreport files created

    The rtreport file is located at server level, if you run munin under one user account inside a cage, that user wont be able to access rtreport files. each cage has its own /tmp directory.
  10. M

    Symlink problem in 4.2

    "DisableSymlinkOverride" does not allow change symbolic link related configuration via .htaccess "VhostRestrained" does not allow linking to anywhere beyond user's home directory.
  11. M

    Download starts delayed

    You need to check ip_conntrack limit, check output of 'dmesg', if the limit has been hit, you need to google it for solution. Also, with your server, we recommend enabling "AIO" if you are serving tons of static files.
  12. M

    [solved] Cpanel + LSAPI 6.0 + LSWS 4.2 Anomaly

    run make under php-xxxx/ directory.
  13. M

    [solved] Cpanel + LSAPI 6.0 + LSWS 4.2 Anomaly

    I do not think there is any change related to memory usage between lsapi 5.5 and 6.0 . you have to test it on the same server with same PHP release. to get back to 5.5, you can manually download php-litespeed package and over write *.c and *.h under php-xxxx/sapi/litespeed, the run make, copy...
  14. M

    LiteSpeed Slow

    WHM/SSH, should be a temporary root password.
  15. M

    LiteSpeed Slow

    you can send it to bug@litespeedtech...
  16. M

    LiteSpeed Slow

    can we login to take a look?
  17. M

    [solved] SetEnvIf Alternative

    you can use a rewrite rule to do the same thing.
  18. M

    modsec issues

    We can add an option in next release.
  19. M

    modsec issues

    you can try a rewrite rule. LiteSpeed modsec engine only block URL that does not result in 404 or static file.
  20. M

    Urgent Problem with Litespeed and OS X 10.8

    check error log and stderr.log, enable debug logging if need. make sure PHP binary is working properly.
Top