Search results

  1. M

    Disable access.log ?

    You can set LiteSpeed server level log file to /dev/null. We will change LiteSpeed to stop logging under lsws/logs directory for vhosts configured through Apache httpd.conf
  2. M

    Ignored Apache Modules

    Update again, yours is not the latest.
  3. M

    Ignored Apache Modules

    It is a feature back port from 4.1RC release, it was not ported properly, just fixed this, do a force reinstall, it should work now.
  4. M

    [RESOLVED] PHP Installation Errors

    install libz-dev
  5. M

    undefined MIME Type errors after upgrade

    Those warnings are harmless, you can ignore those.
  6. M

    [INFO] Remove pid: xxxxx

    LSWS is tracking dead PHP processes, nothing wrong. no worry.
  7. M

    [Resolved] htaccess - allow access from a certain IP address

    get rid of <Files *> </Files> It is not necessary. see if it works.
  8. M

    [ERROR] [MOD_ACTION] The second parameter must be URL:

    Try a "Force Reinstall" from web console, version management.
  9. M

    [ERROR] [MOD_ACTION] The second parameter must be URL:

    Add "fcgid" to the "Ignored Apache Modules" configuration from LSWS web console. It is a new feature added under "Using Apache Configuration File" section.
  10. M

    [ERROR] [MOD_ACTION] The second parameter must be URL:

    Yes, it is in the main server section, applied to all vhosts. What does it looks like? The Action direction should use a CGI URL for the second parameter.
  11. M

    ls php sapi versions

    use the code from litespeedtech.com. the code in php.net can only be updated when new PHP release is available, eventually, will catch up.
  12. M

    [ERROR] [MOD_ACTION] The second parameter must be URL:

    Looking for "Action" directives in the apache configuration file. And it is safe to ignore those errors as well.
  13. M

    disabling features

    It is not possible with LiteSpeed while using Apache httpd.conf. you have to disallow Options override.
  14. M

    disabling features

    For example: Options -Includes -ExecCGI to stop mod_include and CGI.
  15. M

    Apache not able to handle many connections and i want to buy litespeed but..

    for vbulletin/IPB, you can use 1-CPU license for your server. http://www.litespeedtech.com/support/forum/showthread.php?t=1660
  16. M

    PHP suexec extensions

    Yes, 4.1RC3 build has been updated as well.
  17. M

    PHP suexec extensions

    4.0.17 release added php53 suffix, removed php3 suffix, should be enough for current available PHP releases.
  18. M

    [Resolved] expires header not working for js/png files unless htaccess is in place ?

    It is by design, we want LiteSpeed behave exactly the same as Apache when load Apache httpd.conf. However, enabling expires header by default regardless Apache configuration may not be bad idea either. it only helps. So, yeah, we may turn it on by default in next release. :)
  19. M

    [Resolved] expires header not working for js/png files unless htaccess is in place ?

    those warnings are harmless. Are you using LiteSpeed with hosting control panel? or configure everything in native configuration? How the expires configuration being set?
  20. M

    [Resolved] expires header not working for js/png files unless htaccess is in place ?

    Please check and make sure the MIME type is defined for javascript and png in LiteSpeed main MIME configuration file. Try new 4.0.17 release.
Top