X-Real-IP HTTP header

  • Resolved keychange

    (@keychange)


    8 years, 1 month ago

    I am running centos vps with nginx with over 20 WP installs with Wordfence. On all other installs WF suggests X-Real-IP HTTP header however on one site it suggests PHP’s built in REMOTE_ADDR. However if I let WF change to these settings my VPS IP starts showing up on the blocked list.

    It has been doing this for a couple of months and I can’t think why one domain is being incorrectly detected. Today I noted an alert Notice: Undefined variable: check_exts in /home/mydomain/public_html/wp-content/plugins/mainwp/page/page-mainwp-api-settings.php on line 35 Notice: unserialize(): Error at offset 0 of 21 bytes in /home/mydomain/public_html/wp-content/plugins/mainwp/class/class-mainwp-api-manager-plugin-update.php on line 115 0

    So I set it back to X-Real-IP HTTP header and the error above disappeared – but the alert stating I should PHP remeains.
    All updates are current on all sites – plug ins are common to other sites

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘X-Real-IP HTTP header’ is closed to new replies.