Search results

can you give me access to web admin console ( :7080), just to check the settings, no modification.

can you try 4.2.8 and see if the issue still exists?

yes -- Load Averages: 0.67 0.71 0.70 the load is below 1, quite low.

if load is below or around 8, that's quite normal.

the errors regarding lsphp55 can be completely ignored on your server. if you just don't want to see them in error log, just do #ln -sf /usr/local/lsws/fcgi-bin/lsphp5 /usr/local/lsws/fcgi-bin/lsphp55 if you disable mod_security, you won't see this error message any more: 2014-04-01...

have you installed any statistic tool like google analytics ? if visits have increased a lot since switch to litespeed, the traffic will increase of course.

looks problem here. please modify and try: Environment: PHP_LSAPI_CHILDREN=8 (this is to match "Max Connections"=8) Back Log: 10 --> 100 Instances: 10 --> 1 i.e., back to default setting as possible

that plugin should be good although old. >the "litespeed_requests" plugin doesn't work at all may due to format .rtreport has changed a bit since then. you can modify the source code to reflect the format change. also, some relating pages in our wiki...

you can ignore lines with "php55" in it -- if you don't use php 5.5.x 2014-04-01 00:19:27.005ERROR[ModSecurity] unknown server variable while parsing: MULTIPART_STRICT_ERROR you can disable mod_security temporarily to see if any improvement. have you installed apache as well ? does it work well...

In fact you don't have to install apache, as long as httpd.conf and its included files/directories are there.

put following in httpd.conf <LocationMatch ".*/wp-login.php"> Order deny,allow Deny from all </LocationMatch> I ran tests /abc/wp-login.php /wp-login.php /xxx/wp-login.php/yyy ... all of above have received "403 Forbidden" as expected, under both apache and litespeed. of course, this only tests...

I think there is no difference between 4.2.8 and previous version regarding this rule. change <LocationMatch /wp-login.php> to <LocationMatch ".*/wp-login.php"> should resolve If my wordpress site is www.test.com/wp (or any subdirectory) the rule doesn't work

after recompiling apache, I think need re-install litespeed cPanel plug-in again. have you tried "Auto-Installer"? -- http://www.litespeedtech.com/products/control-panel-plugins/cpanel-whm-plugin

one user told us(on Feb.26) following rules works well: <LocationMatch /wp-login.php> # only match posts SecRule REQUEST_METHOD "(^POST$)" "chain,id:'1303701',rev:'1',phase:1,deny,status:403,msg:'Too many requests'" #set ip pagecount and expiry of 30 s SecAction...

I did tests on both apache and litespeed/4.2.5 you're right. the .htaccess is ExpiresActive On ExpiresByType text/html A2592000 apache will add response headers: Cache-Control: max-age=2592000 Expires: Sun, 27 Apr 2014 02:34:15 GMT for both .php and .html litespeed will add above 2 headers to...

please do #yum install gdb so the debug info will be more detailed and help to fix a bug.

I think current lsws don't support this feature (dynamic web server) -- one big reason: it'll reduce the performance, since dns take time, if every request do dns lookup, it'll drop the performance greatly. any other web server support this feature ? apache ? if IP changes, you have to restart...

try rewriterule assume it's native vhost. vhost->Rewrite ReriteRule /shop/(.*)$ http://nginx_shop_srv/$1 [P] define an external app nginx_shop_srv as web server, Name:nginx_shop_srv Address: 10.0.0.2:80

they are 2 types of virtual host: 1)vhost comes from apache's httpd.conf 2)vhost from lsws's web admin if it's 1), please check first if .htaccess works under apache. if it works, it should work under litespeed.

it's not good to set max conn too high. when WaitQ disappears quickly(not pile up), it's not a big problem. when WaitQ keep increasing, only incresing max conn may not resolve the problem. should try to identify the bottleneck at this time. for example, can check mysql status by "mysqladmin...