Search results

So, if litespeed can increase connection timeout for specific php script, it'll resolve your issue ideally.

please check the related log message in error_log(or error.log) and stderr.log

can you try other 2 suggestions in my previous posts? to try them first anyway if possible. this is to identify where the problem is. if one workaround can resolve the issue, it'll help a lot for the final solution, and tell where the correct direction is.

increase http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout may resolve the issue. what's the value of current setting?

sorry, we may not able to help with vbseo, since this forum haven't installed it. Here we mainly demonstrate lsws's unique rewriterule+cache function, in example of vBulletin which happen to be running as litespeed support forum.

please try increase to 700M/750M, see if difference.

no need to upload boost.php in litespeed case. boost.php is used to generate varnish cache rules.

it's 3.8.4 :)

not sure if set "Retry Timeout (secs)" of the lsphp5 ext app to a big number will help or not --- I've never tried it, just FYI. for long running php script, not sure if you can run it in command line, i.e., lsphp5 abc.php, if so, the connection time out between lsphp5 and lsws won't take...

dihuta: please try same settings at server level in your case, then try rewriterule cache, see if it works. eva2000: for wordpress, I think wordpress's plug-in: wp super cache(or w3 total cache?) is better, please use it instead. why? since it generate static pages --- that means, if a post has...

Thanks for the update. so the initial issue has gone? is the attachment big? there are many reasons which cause 503 error. no enough memory is one of them. what's "Memory Soft/Hard Limit" of your lsphp5 process?

please try increase: http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout to over 60 seconds what's the current value? 30 seconds?

rewriterule has no difference. but need put it in httpd.conf, vhost definition section. it's ok to put the rewriterule in .htaccess as well. just need some minor adjustment, since the per server and per directory rewriterule difference.

1.install vBulletin plug-in(or "vBulletin Boost Product XML") product-boostv1.xml‎ please refer the first post in this thread, to get the file's link and download it(currently, it's 657 views) 2.set cache directory lsws admin console-->Server-->Cache: Cache Storage Settings->Storage...

1. yes. That's where to define your cache policy. Here's an example for litespeed native configured vhost: Cache Request with Query String:Yes Cache Request with Cookie:Yes Cache Response with Cookie:Yes Ignore Request Cache-Control:Yes Ignore Response Cache-Control:Yes 2. the user...

Hello dihuta, wish you're still monitoring this thread. We've tried to cache this vBulletin(litespeed support forum) for guest visits for some days and looks successful so far. Just using the way you mentioned in your post: install a vBulletion plugin first, then using litespeed's unique...

for vBulletin, unfortunately, every guest visitor will be set cookies, so it'll not working as you expected. caching vBulletion for guest users is a bit more complicated, but it's possible under litespeed. In fact, we've tried to cache this vBulletin (litespeed suport forum) for guest visitors...

so the question may be at "Building matching PHP" and I asked you to compare the output of phpinfo() under apache and litespeed. What's the environment and how did you build lsphp5 to match apache PHP.

please compare the phpinfo() in litespeed and apache if any difference. google "mobiquo/mobiquo.php", there are a lot same error reports. here's one: http://tapa.tk/forum/showthread.php?t=4599 it should not be a litespeed specific issue at all.

1. it's possible to cache dynamic page(for example php) at server and each vhost level, without using rewriterule. This thread is talking about cache with rewriterule, which is litespeed specific feature and very useful in practice. 2. cache the original URI -- i.e., the URL in browser's...