Search results

  1. M

    recv_fd() failed

    Please download and try 4.1.9 release packages. Just change the version number in the download link to get it.
  2. M

    [solved] [cPanel] After LiteSpeed installation /whm-server-status gives a 404 error

    LiteSpeed does not support Apache's status page, that's normal.
  3. M

    LS cache on a VPS

    The RAM is little low, but you can set cache storage to use hard disk instead of ram disk, let linux kernel to manage it. Load a trial key and give it a try.
  4. M

    CXS or Litespeed ??

    suhosin.upload.verification_script
  5. M

    CXS or Litespeed ??

    You can try suhosin with CXS.
  6. M

    Intercomm event: 17, abnormal

    Thanks, the bug report is useful. This issue should be addressed with the latest build.
  7. M

    Failed to bring up LiteSpeed.

    Please send in your IP address to sales@litespeed... for verification.
  8. M

    Symlink not following - 403

    Where you put "Options +FollowSymLinks"? If it is in .htaccess, you need to check if "AllowOverride" is set properly. Looks like it was ignored, the default is "SymlinksIfOwnerMatch". Add that to the <VirtualHost...> section should work.
  9. M

    litespeed gone haywire

    CloudFlare's DDoS protection is a joke when face real DDoS attack. You either need to make "/" page load faster, or cache it.
  10. M

    Litespeed Keeps Restating Hourly (Logs Inside)

    cPanel restart LSWS to retate log file, update configuration changes. LiteSpeed does not graceful restart, there is no service interruption during restarts. Nothing to worry about.
  11. M

    litespeed gone haywire

    You can increase the PHP suEXEC max conn, right now is 5, and the WaitQ is at >200. Try 50, then increase it gradually if want. remember, the high the "max conn", the higher the load. it is normal. You can try our antiDDoS service to filter the attack.
  12. M

    Custom error page dont work on cPanel

    Sometime, rewrite rules interfere with custom error pages. For most setup it should work as expected. but, sometimes, need some minor tweaks in LiteSpeed to make it work like Apache. Please turn on debug logging, rewrite logging for the vhost has this problem, then produce the problem, send us...
  13. M

    PHP using the same session IDs?

    Does it only start to happen recently? after 4.1.6 or 4.1.7? It could be caused by some extra event handling coding added to deal with 100% cpu issue. I have reversed some changes that could affect this, please force reinstall 4.1.8.
  14. M

    lsphp: suPHP-like paranoid mode

    LSWS PHP suEXEC does not change UID/GID based on file ownership, instead it always change UID/GID to the owner of the web site.
  15. M

    Problem with KML files

    You can try turning off keepalive of LSWS, google may have difficulty with reading keepalive response from LSWS. I guess.
  16. M

    Trying to use APC but it seems to be clearing out?

    that feature is on our to-do list. no ETA yet.
  17. M

    4.0 vs 4.1

    Yes, updated with the latest fix.
  18. M

    4.0 vs 4.1

    another 100% cpu bug in 4.1.8 has been addressed. It was actually introduced in 4.1.8, related to a change in handling Apache configuration. 4.1.8 is running smoothly now.
  19. M

    4.0 vs 4.1

    First 4.1.8 release build is uploaded. however, it is not the final build yet.
  20. M

    4.0 vs 4.1

    One bug that causes 100% cpu has been fixed in 4.1.8 thanks for a quality bug report. You can give it a try on the server that you have to use 4.1 release. And believe me that we want those bug fixed more than anyone else. The main reason that those bugs has not been fixed is because that we...
Top