Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • The issue here is that when you’re not logged in to the site, incoming requests are going to their READ-ONLY apache port(Since NGINX is used as a gateway in front of Apache).

    Since those requests cannot modify files, they get a permissions error which ultimately leads to the 500 error. Enabling WordPress debugging should have generated the relevant error for that.

    @lapzor – The following NGINX rule should address this problem on the wpengine platform;

    if ($request_uri ~ ‘\?action=koko_analytics’) {
    set $is_trusted 1;
    }

    If there are any other actions via args that the plugin might be doing, there’s likely a need for a rule to do the same for those URIs as well.

    Hello Clarion.

    Please contact Wp Engine Support and ask that the following path be excluded from the server-side caching;

    ^/wp-content/plugins/geographical-redirect

Viewing 2 replies - 1 through 2 (of 2 total)