Search results

Just be careful with the shared memory allocated for each account, it could exhaust physical memory, and bring the server down to its knee when swap memory is used.

You need to check the log file for reason why get 403 errors. it should be in the error log.

It should have "403 0" in access log.

wait for 4.2.5, blockbot will change status code to 403 in the access log. but it is just cosmetic. It will be available today or tomorrow.

first one is fine.

do not judge it based on access log. the "200 0" entry means that LSWS close the connection immediately without sending back anything, just does not change the status code. And you can combine it with [F] flag if you want. No matter how big the botnet, they will reuse IP.

change the last line of your rewrite rule to LSWS enterprise will reset connections from that IP, refuse to serve any request. more efficient than [F] flag. it is a LiteSpeed specific feature.

http://blog.litespeedtech.com/2012/12/11/switching-from-apache-open_basedir-in-the-shared-hosting-environment/

If you client was using mod_wsgi with Apache, the answer is yes.

no plan on that yet. not aware which setup uses that. Is that for suphp setup? PHP selector?

Likely a PHP/MySQL code issue. Check if any process uses too much CPU, strace it.

Yes, just use something like <IfModule litespeed> , it will be ignored by Apache.

Please try 4.2.5 . /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.5

You need to turn off "PHP suEXEC daemon" mode, it is not the same as suEXEC. You have to use PHP suEXEC to use cagefs.

Please do /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.5 then try AddDefaultCharset again.

with 4.2.5, if "AddDefaultCharset windows-1252" is set in .htaccess, the index page will add that charset. If this is a dedicate setup for this customer, you can also update the default indexing script at /usr/local/lsws/share/autoindex/default.php to set "Content-type" header with charset. it...

If you do not use per user php.ini, you can enable PHP suEXEC daemon mode after compiling PHP with LSAPI 6.3 . http://www.litespeedtech.com/docs/webserver/config/extapps#runOnStartUp It will prevent APC cache from being flushed.

You can safely ignore it.

Yes, if we could not address it in 4.2.5 release, will definitely do it in 5.x release.

192.168.1.*T or 192.168.1.0/24T