Search results

4.2.5 is quite stable. you can switch between 4.2.4 and 4.2.5 by one-click at any time

in include/.htaccess, put Deny from all should show 403 Forbidden when access ../include

since lsapi 6.4 has upgraded a few times, you can Build Match PHP again to ensure it's built with latest lsapi 6.4. then do a force-reinstall 4.2.5. for this error message, you have to increase Server->Tuning->Connection Timeout (secs):120 as we discussed before.

actually there are 2 formats of rewrite rules: per-server and per-directory. the example you give is per-directory format, should put into a .htaccess file not into "the LS panel" which is per-server format.

maybe those are php session files -- it's safe to delete old ones. you can create a cron job to do it --- for example, delete all /tmp/php* is older than 24 hours.

the particular issue is fixed -- I logged in the user's server and helped him to resolve the issue and he's satisfied with it. if you ask for 100% compatible, usually it's not possible in practice since the complexity. that should be no choice other than stick to apache. there are some big...

how frequently do it happen ? restarting lsws fixed the issue ... then after restart, how long will it happen again ? do your lsws restart frequently, or it won't restart for many days ?

by default, query string is part of URL and litespeed cache is based on domain + URL. different query string will be cached separately. >I can't find a way to force WP Super Cache to super cache URLs with query strings not sure about this. so if wordpress not configured to use friendly url...

looks php crashed. keep monitoring it, if high frequency, need review what changes has made recently, and try to revert back the changes, then monitor ...

thanks for the suggestion. here's a recent blog post related though not the answer of your question http://blog.litespeedtech.com/2013/10/28/cpanel-support-the-official-position/

in general, litespeed has no such issue --- will fill up /tmp folder after long run. there must be something special on your server which caused the issue. when it get to full or nearly full, can you check what files under /tmp ? then you may get ideas what the root cause might be.

should be same issue described in http://www.litespeedtech.com/support/forum/showthread.php?t=6593 it can be further simplified by: www/test/.htaccess <Files *> Order Allow,Deny Deny from all </Files> www/test/test2/.htaccess <Files *> Order Allow,Deny Allow from all </Files>...

a WHM/cPanel server ? so the error only in /usr/local/apache/logs/error_log? some errors in this file with "APVH_" in it, so you can know which virtual host.

here USER mean IP. can limit each IP's connection number, soft reqs/sec, hard reqs/sec at server level(i.e., regardless which virtual hosts). no way to limit "req in processing". but limit soft/hard reqs/sec can limit it indirectly.

that might be 4.2.2's implement has bug in it. can you give an example file which cause this 403 error, its ownership, and should it return 403 ? with this detail information, we can know if it's a 4.2.2 bug or 4.2.5 bug.

I tried to upload a 369kb png to a wordpress 3.7.1 installation, tried both uploader, no problem. just ask, will restarting lsws fix it temporarily ?

does restarting lsws resolve it ? this is not a solution suggestion, just for investigation purpose. check this setting: lsws admin console->Server->Tuning->Max Request Body Size (bytes) default is 500M this feature is litespeed specific than apache.

the VPS's bottleneck is memory, only 490M: ~>free -m total used free shared buffers cached Mem: 490 459 31 0 7 157 -/+ buffers/cache: 294 195 Swap: 1023 14 1009 while...

yes ... otherwise php will run as nobody, will cause numerous problems in a WHM/cPanel environment.

the way to enable suPHP in litespeed: lsws admin console->Server->General-> PHP suEXEC: PHP suEXEC Max Conn: what's their value set on the server ?