Search results

It is being released to public, it may show up in version manager within 24 hours. You can upgrade from command line /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.6

The "drop-in replacement to Apache" is in the sense that LiteSpeed is compatible with Apache's configuration, but not that LiteSpeed must not take what Apache does not. You can always validate configuration using Apache's binary at anytime. To some degree, we will put more effort on detecting...

You can google scripts written for Apache, most likely, it will work just fine with LiteSpeed.

Only the user account being attacked may experience slowness, other users should not get any connection level error. Maybe it is caused by bugs in 4.2.5, so upgrade to 4.2.6 may fix it.

cloudlinux limit should be twice as high as the PHP suEXEC max conn or worker group works. .

please try force rebuilding PHP again, should be using 6.5 now.

Do not configure LSWS PHP worker above the limit set in CloudLinux, set it lower and leave some head room. The fork() error is likely due to CL limit.

Just add ErrorDocument 403 "" in .htaccess

Please refer http://www.litespeedtech.com/support/forum/showpost.php?p=75743&postcount=20 might be the case for yours.

You current setup may not have .htaccess enabled, so those rules wont work in .htaccess. If you use pure LiteSpeed setup, not using Apache configuration, you can convert the rewrite to a vhost level rewrite rule. htaccess support can be disabled to get better performance. Just add "/?" to your...

Likely something wrong with the PHP or MySQL code if the request should not take more than 120 seconds to finish. The second log entry tells that the request was not aborted.

set http://www.litespeedtech.com/docs/webserver/config/general#extAppAbort to "no abort", see if it helps or not.

check pstree output, that user should get its own PHP process group started by lscgid or from litespeed process.

LiteSpeed is more fault tolerant than Apache. There are some reasons behind it. The first case is that LiteSpeed has logic to break the loop redirection, it is feature, not a bug. I do not think that Apache can detects it, have to rely on browsers to detect that. The second case is that if...

Which PHP suEXEC mode is used? regular, through CGID daemon, suEXEC daemon mode? Do you have error log and stderr.log when the server is using 4.2.5, please send it bug@litespeed....

You can use the "build PHP" feature from LSWS web console. it will apply latest LSAPI. When you apply LSAPI 6.4, you only need to copy over *.c and *.h, do not change Makefile.frag and config.m4 .

Latest whm plugin does register itself, so there is no need to allow permit_unregistered_apps_as_root change is not required. 4.2.5 comes with the latest whm plugin, should address this as well.

There are big changes in the plugin, can you try reinstalling it from command line?

our 5.0 release will make it possible as it allows third party modules.

Yeah, we will keep that in mind. Thanks!