not compatible with Buddypress

  • Hello,

    I met the problem of Redis Object cache with Buddypress.

    For your information, We are running wordpress MU site with HHVM + Redis cache, and using the “D” way of buddypress installation by following the official instructions:https://codex.buddypress.org/getting-started/installation-in-wordpress-multisite/

    the following is our testing process:

    Only nginx helper(https://www.ads-software.com/plugins/nginx-helper/) and Redis Object cache are activated in network dashboard, and only Buddypress is activated at buddypress root site, please check here:
    https://prntscr.com/e075t5
    https://prntscr.com/e076ij

    When I enable Object cache, and then activate Buddypress, I will not be able to access both the posts and pages at backend in buddypress site, it just show a blank screen.
    Please check here:

    https://prntscr.com/e078gc
    https://prntscr.com/e0795f

    in this case, it always show 502 Bad gateway errors or just a white screen at frontend, actually, this is the reason why we begin to have a complete testing process.

    when I disable Object cache, the buddypress will works fine. I reinstalled buddypress for several times, and all tests are under the theme of Twenty Sixteen.

    So would you please let me know how to handle the problem, greatly thanks.

    Have a nice day.

    Alex

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    This plugin is compatible with a clean install of WordPress + BuddyPress, so the “502 bad gateway” error must be caused by your particular setup. I’d suggest you get your developer to take a closer look at the logs to find out what’s causing the 502.

    Thread Starter alexlii

    (@alexlii)

    Thanks for reply, we have not find anything in logs, but we will continue to check.

    Buddypress official explanation on buddypress caching mechanism, for your reference:
    https://bpdevel.wordpress.com/2016/09/19/group-queries-have-been-rewritten-for-bp-2-7/

    If you find the the problem is related to your plugin after your check, I would like to buy you a cup of coffee for asking your help, it would be great if we can get your further instructions or suggestions!

    Thanks and have a nice day!

    Alex

    Plugin Author Till Krüss

    (@tillkruess)

    It’s most definitively related to BuddyPress. This plugin is just an API, the caching itself happens on BuddyPress’ side.

    Thread Starter alexlii

    (@alexlii)

    Thanks a lot.

    Here is error logs, and it would great if I can get your further suggestion:

    2017/01/26 17:30:49 [error] 4982#4982: *136518 no live upstreams while connecting to upstream, client: 123.120.70.32, server: lovcour.com, request: “GET /bpmember/papa/ HTTP/1.1”, upstream: “fastcgi://hhvm”, host: “lxp.lovcour.com”
    2017/01/26 17:30:50 [error] 4982#4982: *136518 connect() failed (111: Connection refused) while connecting to upstream, client: 123.120.70.32, server: lovcour.com, request: “GET /bpmember/papa/ HTTP/1.1”, upstream: “fastcgi://127.0.0.1:8000”, host: “lxp.lovcour.com”
    2017/01/26 17:30:51 [error] 4982#4982: *136518 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 123.120.70.32, server: lovcour.com, request: “GET /bpmember/papa/ HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9000”, host: “lxp.lovcour.com”

    Alex

    @alexlii consider using php7 exclusively instead of hhvm. Also increase your fastcgi buffer values to get rid of that error reading response from upstream

    • This reply was modified 8 years, 1 month ago by blindpet.
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘not compatible with Buddypress’ is closed to new replies.