Search results

  1. M

    LiteSpeed package reqs.

    glibc, if need to compile PHP, you need m4, autoconf, gcc, ld, etc.
  2. M

    Invalid key after update

    You need to remove all license.key file under the expanded installation directory as well as the directory that LSWS installed to, usually either "/opt/lsws/" or "/usr/local/lsws".
  3. M

    Invalid key after update

    Please send your serial to sales@litespeed...
  4. M

    How to check the license core ?

    Number of lshttpd processes minus one is the license core value.
  5. M

    async io writeav setting

    As well as support for upload progress bar. May or may not include the new realtime status page, depends on our progress.
  6. M

    failed to find flength, ffmpeg-php not compatible with LiteSpeed?

    You can try the latest 4.1b1 release, upload progress bar should work now. Just change the version number in the download link to get it.
  7. M

    Invalid key after update

    Please clear your license with http://license.litespeedtech.com/migrate.html remove all your old key. then register a new key. move the new key to conf/ directory.
  8. M

    long running php process getting killed

    You can try increase "Initial Request Timeout" for lsphp application http://www.litespeedtech.com/docs/webserver/config/extapps/#initTimeout
  9. M

    503 Service Unavailable The server is temporarily busy, try again later! Powered By

    Please follow the trouble shooting guide http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi#trouble_shooting
  10. M

    async io writeav setting

    4.1RC1 will be available in a few days.
  11. M

    About the license and CPUs

    VPS is the same as 1-CPU before the connection limit reached. PHP/MySQL should be able to use all available CPU.
  12. M

    503, but no logs, or explanation...

    Are all rails app run as the same user ID? Maybe you should increase the "Process soft/hard limit" under the rails tab. Since it works sometimes, I think it is a resource limit problem.
  13. M

    How to Configure 4.0 Cache

    http://www.litespeedtech.com/support/forum/showthread.php?t=2255
  14. M

    FilesMatch & php .htaccess options

    OK, it has been uploaded.
  15. M

    FilesMatch & php .htaccess options

    Please wait for 10 minutes to have the updated version uploaded.
  16. M

    FilesMatch & php .htaccess options

    updated 4.0.4 has addressed this. you can give it a try.
  17. M

    FilesMatch & php .htaccess options

    It is the LSWS disk cache feature, not WP cache plugin, disabled it for now. The problem that WP redirect www.domain.com to domain.com, if LSWS cache the redirect, it will cause trouble. We have to change the cache code to put requests to www.domain.com and domain.com in two separate cache.
  18. M

    FilesMatch & php .htaccess options

    Have you enabled disk cache? If yes, you should disable it for now. I think it caches response for request http://www.mp3smackers.com/, which redirects to http://mp3smackers.com/
  19. M

    async io writeav setting

    It has no effect for 4.0.4.
  20. M

    FilesMatch & php .htaccess options

    Then, you should not mix them together, it only make it harder to identify the cause of the problem. The screen shot shows that the redirect is actually sent by PHP, LSWS is just the messenger. What the actually command of "HEAD"? I think it is just a command alias. I tried "curl -I...
Top