Search results

If you want to change anything, just do it in WHM/cPanel.

Those vhosts are configured through Apache's httpd.conf, and only show under the status and report pages.

The configuration option to enable it is --with-eaccelerator-shared-memory, our current binary was not built with that option, you need to build your own.

I knew what's wrong, please check /usr/local/apache/conf/mod_security/exclude.conf , if you have that file, please comment out the <locationMathch "/index.php"> section. If not, search for <locationMathch "/index.php"> in other Apache configuration files and comment it out.

You'd better do a fresh reinstall without importing Apache configuration during installation. There are a lot of Apache vhosts not supposed to be configured in lsws/conf/httpd_config.xml.

You are welcome. After remove the default listener 1080, it works now. You made two mistakes during the installation, First, you use 1080 instead of 8088 for normal HTTP service, then use "port offset" = "1000", end up with port 1080 as well, so it conflict with the default listener. second...

I guess I knew what is wrong, go to LiteSpeed Admin console and remove the "Default" listener which uses port 1080. restart, it should work.

You should not import your Apache httpd.conf during the installation, maybe you did not, just a quick remindar.

If you dont mind, you can PM me a temp root access so I can take a look, it is the fastest way to get the issue resolved.

Is this problem LiteSpeed specific or just same thing happened with other platform like mongrel or WEBrick? We are not RoR experts, seems to me that the "escape()" function encode space into %20 .

those errors should not make all vhosts stop working, just related vhosts. Please run LiteSpeed on a different port with "Port Offset" so you can verify whether it works or not. Please post more information regarding the vhost having problems.

You should just remove the password of your old private key, a new private key will not match the certificate created for the old key, they won't match.

You should turn off output_buffering if you want to avoid the delay of initial byte, or call flush() in your PHP code.

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ssl_private_key

One flaw in your test is that, Apache is PHP 4.4, LiteSpeed is PHP 5.2.2, it is not an apple to apple comparison. According to our experiences, PHP 4 is faster than PHP 5.

Please double check if PHP output buffer is used for the LiteSpeed test.

You can run LiteSpeed with port offset and turn on debug logging with "Debug Level=HIGH", for the vhost have rewrite problem, add "RewriteLogLevel 9" to the vhost configuration section in httpd.conf. If you cannot figure out what is wrong, please PM me the real URL, I can take a look.

You need to remove the password protection of your private key first.

Does not help much on PHP as PHP run in their own processes.

I do not have a quick answer to your questions since we do not create a MIB for our SNMP stuff. But there is a better solution, check out http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:snmp_cacti_monitoring It is recommended but you don't have to buy n-core license to...