Search results

Start a fresh ruby process is very expensive, so it is not a good idea to let ruby process die frequently. Instead, LiteSpeed will keep one ruby process running, when new request comes, it will fork a child process to serve the request, and the child process quit after idling for a while. When...

Please check the latest 4.0.12 release, if anything still prevent CSF from pickup it, we will fix.

Yes, LiteSpeed will do that.

each SSL certificate requires a dedicate IP:Port combination. So, for domain with dedicate SSL certificate, you need to assign a dedicate IP for that domain.

We have no problem building PHP 5.3.1 that way. Maybe you are using a manually built PHP module, you may need to build it again after build matching PHP 5.3.1 . Run PHP 5.3.1 from command line, see what you got. /usr/local/lsws/fcgi-bin/php-5.3.1 -i

Put up a simple phpinfo() page for testing. check /path/to/lsws/logs/error.log for errors.

Latest 4.0.12 build should take care of it. Yes, you need to do a manual update to the latest build. For future releases, it should work fine.

that's bug in our version management code, need to fix it with new build of 4.0.12.

Yes, you can use the free version to setup/configure PHP/MYSQL Or use the 15-day free trial on the new server. You have to manually take care of the old server when you migrate the license, either download to standard or use trial. If you migrate the license, you got 3 days on the old server.

LSLB uses a "Ping URL" to verify backend periodically, expecting a "200 OK" response. if it failed to connection backend server, or backend server timedout or return something other than "200 OK". LSLB will mark that backend server as "unavailable". LSLB will log the error in error log. LSLB...

Yes, LSWS or LSLB log attacking IP addresses to main error log.

Do you have a valid license? or on trial? used trial 30 days ago? Use i386 binary on x86_64 or vice versa? Those are possible causes. Try start lshttpd from command see what error you got, check /usr/local/apache/logs/error_log.

add "Web server" external application, use address 127.0.0.1:8080 for default tomcat installation. Then add "Proxy" contexts for URL should be served by backend web server.

Yes, download and do an upgrade.

"nolog" issue was addressed in latest 4.0.12 build, "DROP" action will be added in 4.1RC3.

It works properly, I can do that in our lab without any problem. It must be something else, maybe rewrite rule or other configuration causes this. Maybe you should remove that vhost and configure it again from scratch. You can try proxy instead of AJP as well.

I mean you should keep you current setup instead of trying to use just one server. You configuration looks fine. You can try increase "Max connections" if you still have the "Running short of concurrent connections" problem after upgrade to latest 4.0.12 .

This should have been addressed in the latest 4.0.12 build, please download and upgrade manually again. We will add DROP support to 4.1RC3 release.

It should does what you want. Make sure browser does not cache the result. Make sure that you do NOT add a script handler for ".do", it requires the existence of the script file.

Are you using exactly for the URI configuration? I cannot tell from the image.