Search results

The maximum value of memory limit is 2GB, it is the maximum value of an signed integer for a 32bit application, 2GB should be enough for most applications.

Please try the latest 3.3 build package, the problem might be fixed already.

Fixed in the latest 3.3 build. please download and give it a try.

Changes has been made to the latest 3.3 build, you are welcome to give it a try.

Are you using "PHP suEXEC"? If you are, you need to increase "PHP suEXEC Max Conn". If you can identify those NAT IPs, you can add them to trusted list at server level access control.

Are you using LiteSpeed with hosting control panel or LSWS along? First you need to take care of the DDoS if there is any. Take a look at http://www.litespeedtech.com/how-tos.html#qa_dos And you need to increase the "PHP_LSAPI_CHILDREN" and "Max Connection" maybe from 80 to 150. The server...

Please try the latest 3.3 release build, if the problem persist, we will take a look. http://www.litespeedtech.com/packages/3.0/lsws-3.3-ent-i386-linux.tar.gz

It will not be part of 3.3 release. Maybe in 3.4 release as it requires quite a bit of effort. :)

Thanks for the update. Our 3.3 release should able to handle the httpd.conf with hardcoded port 80/443 as well.

OK, the latest 3.3 package has been uploaded: http://www.litespeedtech.com/packages/3.0/lsws-3.3-ent-i386-linux.tar.gz For 64bit package, just change i386 to x86_64 in the link. If the problem persists, please send the httpd.conf to bug {at} Litespeedtech {dot} com for analysis. :)

There might be compatibility issue between the latest cPanel release and 3.2.4, I will make the 3.3 release package available soon, please give it a try. I assume that LSWS is configured to use Apache httpd.conf directly, right?

It does not matter what SSL certificate is use with LSWS. LSWS does not know and do not care the type of certificate. a SSL certificate is bounded to a listener, that's all what LSWS does, as long as the listener serve the desided domains, it should be fine.

What billing software are you using? WHMCS? Have you checked the httpd.conf generated by cPanel to make sure the configuration for that site is there? Have you set "Auto reload with configuration changes" for LSWS? Will a manual restart of LSWS fix it?

Some 400 error was result of invalid HTTP request, and LSWS does not even bother to finish the parsing when it happen, so it is kind of hard to have it in the access log. Maybe in the error log.

Since LSWS ignore the leading "www.", www.domain.com in the list is optional, but it does not hurt having it there. The order of the list should not matter.

I think it up to how cpanel generate the apache configuration. Some thing like <VirtualHost ip1 ip2 ip3> ... </VirtualHost> works fine.

Set status code to 200 with "X-LiteSpeed-Location" should work. Rails may change the status code to 3xx when "location" header was set, that will result in "Location" header being sent. The 404 status code is because that 404 handler was used for Rails application, you can use rewrite rule to...

OK. the i386-freebsd package has been updated to address the problem. The binary referenced libgcc_s.so due to a problem in our gcc 3.4.6 based new cross compiler for FreeBSD platform. Fixed.

Then you need to find out why it ends up with 403? file/directory permission or something else?

The problem with requests end up with 400 code is that LSWS does not process the request any further to determine which vhost it belongs to, so it is not likely going into the respective vhost access log, it could be logged into the server access log as unclassified requests though. Do you...