Search results

Must be the abnormal behavior of PHP make LSWS think all PHP processes are in the bad shape, so end up with 503 error. Have you enabled "503 Auto Fix", the server will restart automatically attempting to fix the 503 problem.

Have you gotten any chance to check the problem with 3.3 again? If you want to, we can logon to your server to take a look, 3.3 release is due soon, we want to make sure the upgrade from 3.2.4 to 3.3 is as smooth as possible. So, please PM me if you need any help.

get the 3.3 release by change the version number in the download link.

The latest 3.3 package has this implemented already. Just download again.

OK. We will turn safe mode off internally for the auto index script. It will be enforced for other PHP scripts.

Please check the error.log, anything abnormal during startup, I think something wrong with the phpLsapi external application. Configuration failure?

Would you mind letting litespeed staff take a look at your server? If yes, just PM me a temp login.

Are you using LiteSpeed with Apache httpd.conf? Is .htaccess enabled? If yes, what is in there?

Which version of PHP are you using with Apache? My suggestion is to build same version of lsphp with exactly the same configuration used for mod_php (except those API specific parameters). You can get the configuration parmaters from a phpinfo() page. You can also try our 3.3 release package...

It should be something else. Make sure to run "make clean" if you change the configuration.

You can use one copy of code, just add a "Rails" context to each vhost using it. Just make sure all vhosts are owned by the same user. If you want to pursue the proxy route, you have to assign the vhost of the Rails App a different IP other than the IPs of vhosts using it. When you assign the...

It turns out that the "Notice" message at the end of configuration output can be safely ignored, the lsphp binary built just fine.

If you don't mind, please PM me a temp root login, I can take a look. Another customer has this problem because he used the 32bit binary on a server with 64bit Linux. Not sure what is the cause of your problem.

Yes, that is it.