Search results

You are welcome! :-) Usually, the admpass.sh works fine, but it may fail under certain environment. Would you mind showing us the content of the htpasswd file generated by admpass.sh, it can help us fixing the bug. Thanks! George

Please check the password file, at lsws/admin/conf/htpasswd, see if the password file is in good shape. Also, be careful with file permission. Is lsws installed as your non-root account?

Please try increasing memory limit under "Server"->"Security"->"CGI Resource Limit". Please do not use lsapi PHP with 2.1RC1 in production, wait for 2.1RC2.

I think it is a connection problem between PHP and DB, I believe most PHP processes were hanging on DB connections. You can verify it by run "killall php" from command line, then 408 error will disappear. If that is the case, you need work on PHP's PGSQL integration.

Please check configuration under the "server"->"tuning" tab. Yes, it works for dynamic content .

Current release of PHP LiteSpeed SAPI cannot spawn multiple children processes, but this function will be added. So, you need to set "instances" to match "max connections". It is not recommended to set "Max connections" to 2000, unless you have a super powerful server, and usually you don't...

Paypal has something similar to 2CO and authorize.net now, we probably will try that in the near future. Thanks for the suggestion. :-)

There is no option to control that. From what we had learned in the past about large request header, those are bad requests, some of them with too many "Host: xxxx" header in it. Don't know those are caused by a buggy client or intentional attacks. I think 8192 is big enough, anything...

Please use URL rewrite for now, Apache compatible BrowserMatch will be added soon.

For various reason, LSWS always try to start additional FCGI process when "instances" > "1". If you set both "max connections" and "instances" to "1", then only one instance will be started.

It is normal, admin_php is the internally defined PHP FCGI External App for the web admin interface, whenever web admin interface is accessed, you will see those processes, your configuration has no effect on those.

Main differences are: LSAPI, PHP LiteSpeed LSAPI and a stateless load balancer. More information about LSAPI: http://www.litespeedtech.com/lsapi/

Currently, we only accept paypal or bank transfer. We are considering charging credit card directly in the near future. What is your problem with paypal?

Thomas, Do you have to kill PHP processes with "SIGKILL" or just "SIGTERM"? LSWS always try to stop all fcgi processes stated by itself with "SIGTERM" before it quits. So, unless LSWS lost tracking to PID of those processes, or those processes does not respond to "SIGTERM", those processes...

We will figure out the problem with version 3.5 There is no enterprise 1 cpu license, it starts from 2 cpu license. actually, N cpu license means that web server itself can take advantage of N CPU, and it can be used on system with any number of CPU. LSWS with 2 CPU license can bring the best...

Thanks.

Thank you for your updates. :-) LiteSpeed use a standalone CGI deamon, for each CGI execution, litespeed need to make a connection to CGI daemon, forword CGI request to CGI daemon, then CGI daemon fork() then execute the CGI. This kind of design is intended to reduce the cost of fork() by...

Thank you for posting your benchmark results. :-) There are a couple issue need to be addressed. First, It is not good idea to benchmark the helloworld CGI, it is written in plain shell script, very very slow, you should benchmark a CGI written in C/C++. The out of box LiteSpeed...

Glad to hear that you are happy with our product. Please keep us posted if you found what exactly is the problem with vbulletin 3.5, Thanks. Nice forum, even though I don't know that language. ;-)

We had investigated this issue. When X-Forwarded-for header exists in request header, Apache will append the IP of the proxy server where the request comes from when it rebuild the proxy request header. LiteSpeed reuses the request header received, do not rebuild the whole header when...