Search results

  1. N

    User nobody during install process..

    standard version not work well with WHM -- it only creates 5 vhosts from apache's httpd.conf when install litespeed to drop in apache, usually go to http://www.litespeedtech.com/products/control-panel-plugins/download install "cPanel/WHM Plugin" first not sure why "nobody" not work. usually...
  2. N

    User nobody during install process..

    check if nobody exists in /etc/passwd what's the OS ? centOS or ubuntu or ... ?
  3. N

    Installing memcache

    add extension=memcached.so to php.ini
  4. N

    LiteSpeed File Not Found Error (have appropriate rule in htaccess)

    please try to change Force Strict Ownership: Yes to Force Strict Ownership: No and restart lsws
  5. N

    blank page and "PHP Warning: Cannot modify header information"

    above logs should be generated by apache assume you are running cPanel ... then lsws and apache will write error logs to same file: /usr/local/apache/logs/error_log for this issue, you'd better resolve it under apache, then switch to lsws.
  6. N

    LSWS 5.0RC1 - Missing NPN Extension in SSL/TLS Handshake

    I don't understand it yet ... however I'll highlight this thread to developer ...
  7. N

    LiteSpeed File Not Found Error (have appropriate rule in htaccess)

    please post your current settings of lsws web admin -> Server -> Security -> File Access
  8. N

    error on litespeed

    first 4 lines error messages is because of /usr/local/lsws/fcgi-bin/lsphp55 not exist. can ignore them. to workaround, you can #ln -s /usr/local/lsws/fcgi-bin/lsphp5 /usr/local/lsws/fcgi-bin/lsphp55
  9. N

    Xenforo posting error with litespeed, only in some threads

    search 'MATCHED_VAR' '!@rx ://%{SERVER_NAME}/ in mod_security rule file, or disable mod_security rule completely in apache's httpd.conf
  10. N

    [solved] Modsecurity rules to protect WP login?

    may need enable audit log. add SecAuditLog /path/to/modsec_audit.log to trigger the rule, you can run "ab" test, for example #ab -c 10 -n 20 domain.com/wp-login.php
  11. N

    Xenforo posting error with litespeed, only in some threads

    so you tried to put the log under root "/" ! :) not easy to debug but solved ..
  12. N

    [Resolved] images do not display after LSWS 4.2.7 upgrade

    re-read the tip of this setting in lsws web admin, it can explain the issue of this thread exactly ;)
  13. N

    [Resolved] images do not display after LSWS 4.2.7 upgrade

    please try: Force Strict Ownership - No then restart lsws
  14. N

    [Resolved] images do not display after LSWS 4.2.7 upgrade

    the output of above 2 commands are normal. can you post all current settings of lsws web admin -> Server -> Security -> File Access ?
  15. N

    [solved] Modsecurity rules to protect WP login?

    Sorry, I re-read this thread again. I think "Request Filter" for lsws webadmin -> Server doesn't recognize <Location /wp-login.php> </Location> so above file will work with apache's httpd.conf you can comment out above 2 lines in your configuration, and make sure...
  16. N

    [Resolved] images do not display after LSWS 4.2.7 upgrade

    please give the output: #ls -ald /home/user001/public_html replace above user001 to a problem cPanel user's name #ps -ef |grep litespeed
  17. N

    Needs some Litespeed tuning tips

    actually I'm not sure, you have to compare the performance to determine which one is better for your site.
  18. N

    [Resolved] images do not display after LSWS 4.2.7 upgrade

    lsws web admin -> Server -> Security -> File Access, especially Required Permission Mask Restricted Permission Mask change both to 000 to match apache if not 000
Top