Search results

Yes, to upgrade to latest release, you need to purchase yearly software update if you bought the license more than 1-year ago.

Litespeed does not use separate rewrite log, just check error_log, make sure log level is set at INFO or DEBUG.

please check /usr/bin/perl permission.

http://www.litespeedtech.com/docs/webserver/config/adminserver/#enableCoreDump move core dump path, you can change kernel configuration via /proc/ or sysctl.conf

directory with 0755 and file with 0644 permission is world readable. I think the problem might be the permission mask of parent directory.

You need to define "/old/stuff" as a static context, then add apache style configuration like AddType application/x-httpd-php4 php

The limit is going to be 2GB, we raised the limit, it will be enforced.

The latest build of 4.0.13 has 2GB limit, just do a force reinstall to upgrade to the latest. Or wait for the 4.0.14 build.

does it work as expected with Apache?

You should only use it at vhost level. At server level, $VH_ROOT is not set.

You need to set it on web server side. LSLB adds "X-Forwarded-For" request header.

Fix will be in 4.0.14 release.

to trouble shoot the 100% cpu issue, may need the debug build of lshttpd, and attach to the process with GDB. Please contact bug@litespeedtech... for further assistance if need.

It should work well. RewriteCond %{HTTP_REFERER} ^http://(.+\.)?(myspace|blogspot|livejournal)\.com/ [NC] RewriteRule .*\.(jpe?g|gif|bmp|png)$ - [F] is more efficient Have you enabled rewrite in .htaccess? You can trouble shoot it by enabling rewrite log.

You should reinstall LSWS by following http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:apache:ezcpanel if you did not.

http://www.litespeedtech.com/docs/webserver/config/general/#autoReloadApacheConf We recommend "User Apache binary wrapper" for cPanel now.

Thanks! We will apply the change.

We noticed similar behavior from another web site. I think it relates to the cookie sent by browser, PHP somehow does not like it and do something strange. The difficult part is that we cannot reproduce it easily to trouble shoot it further.

You need to compile PHP mysql module and set correct mysql socket path.

Can you give complete code around that line? not that familiar with ruby syntax. :-)