Search results

delete all files under /usr/local/lsws/autoupdate/, restart, see if it makes any difference. if it's owned license, see if the license still valid to upgrade to latest version. and check the date on the server, to ensure it's correct.

no -- since the reason you specified, php/sql is skipped if hit cache. this apply for all cache solution, e.g., varnish. but statistic tool based on java script, like google analytics, is not affected. java script based google analytics, is more accurate to count online users.

1. as replied in another thread, lsws shouldn't affect FTP at all. 2. these errors can be ignored. to prevent it show in error log, just run #ln -s /usr/local/lsws/fcgi-bin/lsphp5 /usr/local/lsws/fcgi-bin/lsphp55 3. vhost listing: in lsws web admin, just click on "Actions", you'll see all the...

lsws don't have any direct relation to FTP. you can switch back to apache to see if the FTP issue still exists.

direct install 5.0 RC3 is ok I put 4.2.21 there for comparison to show the URL pattern. >I installed 5.0RC3 and i noticed there is no updateagent included in the RC3 release... this should be bug

latest 4.2.21 www.litespeedtech.com/packages/4.0/lsws-4.2.21-ent-x86_64-linux.tar.gz for 5.0 RC3, the link is: www.litespeedtech.com/packages/5.0/lsws-5.0RC3-ent-x86_64-linux.tar.gz

Thanks for the update

in this case, clodflare won't help you, since the bottlenack is php-mysql. before discussing about "lsphp5 high cpu", need know or estimate the traffic of the web site. if the traffic is low, I see no much benefit to run litespeed, sticking to apache should be enough. if apache can't run well...

Sorry I don't know the exact answer either for the question at the moment. but likely the answer is No. i.e.: while suExec Daemon works for native vhosts, but all lsphp process run as nobody however for native vhosts, if you prefer each vhosts run lsphp as its own user, that's doable. that need...

so you're using native vhost -- I've not tested with it. it's mainly used in vhost from apache httpd.conf, the setting is simple - just >'run on start up' set to 'suEXEC Daemon'

Server 1 is front end for all visitors and server 2 is back end to communicate with server 1 only ? then enable ssl on server 1 for all visitors connection between server 1 and server 2 have to be http and not https at present lsws proxy support http connection only between front end and back...

those rules works -- I tested before while not test it now. wordpress plugin -- W3 Total Cache had those rules (not sure latest version), I tested and just works.

it should have been fixed long time ago. force re-install latest 4.2.21, then enable gzip globally for a short time. you can revert back easily. the risk should be minimum. I read the "solution", it's not practical. since you've to manually gzip static files yourself.

maybe need add redirect_to( "path") somewhere ? (after headers["Location"] = "path")

how about RewriteRule ^/ /dispatch.lsapi [QSA,L] ==> RewriteRule ^/.*$ /dispatch.lsapi [QSA,L] ?

1. how about >Does Apache return the same error? 2.upgrade to 4.2.21 and test again /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.21

communicating in conversation. tested with webpagetest.org (From: Miami, FL - Chrome - Cable), the page fully loaded time is around 7 seconds not 12-14 seconds. no "5-7 seconds" slower has been confirmed so far. also I suggested to raise LVE limit for specific account and test again. waiting...

you can set a port offset (usually 2000 or 1000), to run litespeed and apache at the same time. then send me the URL of slowest site in Conversation (private message), so I can start to test and examine it.

>When we switch to Apache then sites are around 5 - 7 seconds faster. how many websites on the same host have you tested ? and total number of all websites on the server ? have you compared with apache about the whole server's load / memory / bandwidth usage ? 5 - 7 seconds faster looks a big...

it's normal. litespeed read and parse Apache Configuration File /usr/local/apache/conf/httpd.conf, just like apache do. httpd.conf is a text file, no need mention apache or litespeed.