Search results

the rewriterule for cache looks ok. but we have no experience about dbseo. rewrite rule just one part of whole cache mechanism. only you can test and confirm if the cache works -- if you've done the tests, please inform the community. is the previous issue gone after you removed a few lines of...

I'd confirm something: 1. no such problems on apache ? 2.for guest user only or for both login user and guest user ?

look through the rules again, please try to comment out this line as well: ExpiresDefault "access plus 1 year" can you PM your forum's URL to me ?

according to http://www.php.net/manual/en/function.opcache-get-status.php if put opcache_get_status in disabled_functions, will prevent user to view other users' cached files, but he can't view his own cached files either ? there are only 5 functions of opcache

Thank you for the update! so only xcache is ok for shared hosting. while showing all accounts' cached files is good for your case, it's a security risk in shared hosting environment. :)

comment out this line: ExpiresByType text/html "access plus 1 year" see if any difference.

per https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:rrd-graph-monitoring have you created a cronjob ? after you run /path/to/ls_stats/update.php at leat once, those errors will be gone.

>Permission issue maybe? likely. #chown -R usera:usera /home/usera/public_html/ls_stats may resolve the permission issue.

Hi, that script (/usr/local/lsws/add-ons/rrdgraph/rrdgraph_install.sh) is an independent script, so may not work with cPanel munin service at all. when you install the script, it will prompt you Destination [/usr/local/lsws/DEFAULT/html]: input something like /home/usera/public_html...

from M4hdi in PM(conversation): "I Restart My Server - Then Start lsws - and my websites is up with litespeed."

>Should i set PHP_LSAPI_CHILDREN to be exactly same value with "max connections"? yes.

you can set port offset to 2000(for example), then run apache and litespeed in parallel. create a /phpinfo.php page, compare the output between apache and litespeed, to verify if "build match php" has been done properly. also, you can PM me lsws web admin's access, so I can take a quick look.

you can switch back to apache, to resume your websites first

please try PHP suEXEC : No -> Yes then restart litespeed

please give the screenshot of lsws web admin->Server->General->Using Apache Configuration File

Thanks for the update :) image/icon=A604800 can be removed, since it's duplicated with image/*=A604800 also lack of application/javascript=A604800 so reverting back to the default settings(same as Development) is ok.

86400 seconds means 1 day or 24 hours. can you search all .htaccess directives relating to "expire" and "cache-control"

good progress about cache stopping work. for lsws cache for vBulletin + vbseo, the guide is https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:no-plugin-vbseo from the previous posts, it looks like you've followed lsws cache for vBulletin. please compare with above wiki...

"not set" mean inheriting server's setting. I can log into your server to take a complete check regarding the cache issue. Please PM me the access if you're ok.

has identified the cause. the minimal fix is: /usr/local/apache/conf/userdata/std/2/ivrp>diff cp_php_magic_include_path.conf cp_php_magic_include_path.conf.000 13c13 < php_value include_path ".:/usr/php4/lib/php:/usr/local/php4/lib/php:/usr/lib/php:/usr/local/lib/php:/home/ivrp/php"...