Search results

That probably is 300Kbit/s, those probably just TCP protocol overhead cannot be counted by LSWS, but visible to those tools.

Does the account get created despite the errors? If it is, nothing to worry about.

If you use "Apache Port offset", you need to change port 80 to the real port used by Apache.

Rails is memory and CPU hungry, whether is enough, it is really up to how much resources are required by your application.

Yes, it works, you need compile lsphp with matching configuration. Please check our wiki for instructions.

That's normal for a media server, incoming is very low.

Jut change the version number in the download link to get 32 or 64 bit linux package.

Right now, readable permission by nobody is required by the LSWS web admin console. We will remove that restriction. For Now, you can manually change lsws/conf/httpd_config.xml to use /etc/httpd/conf/httpd.conf.

Are you using a "Port Offset"? You need to find out who send out the "Dedicated Server Page"? Apache or LiteSpeed. If it is Apache, maybe some details in the Apache httpd.conf need to be addressed for vhost with dedicated IP.

You should remove the configuration value for "Apache Handled Content", the second one can be ignored.

You should search the cronjob log for the reason why cron jobs not working, maybe related to PHP verion, module or php.ini.

Maybe you need to build your own lsphp binary to include all required PHP modules. checkout our wiki for tutorials. You can write a shell script or whatever script language you prefer, to parse lsws/logs/error.log, looking for IP addresses hit the "Connection hard limit", automatically ban...

OK, we add that on our to-do list.

Is there any PHP code calls "feof" "fgets" in a loop, it might be a bug in your PHP code.

Maybe you should close all your browser window and start from scratch or try it from another computer. Your account login is working fine.

PMed you the login id.

Just checkout this in our howto http://www.litespeedtech.com/how-tos.html#qa_dos

Looks like PHP internal is looping when feof() is received when reading a request body. We will dig into that when we get a chance.

Glad you made it work and it helps. If would like to post a testimonial, www.webhostingtalk.com is the best place. Thanks!

If you downloaded the 3.3 release package earlier than yesterday, you should download again, it has been actively updated. If you downloaded it yesterday, I may have to take another look on the 503 issue