• Resolved brian90069

    (@brian90069)


    I began getting 503 lockout notices on multiple client sites as Wordfence began reading the server’s IP address instead of the users’ IP address, so brute force atacks were locking the server IP. I’ve been renaming the Wordfence plugin file to allow access and then setting the IP acquiring option to “Use the X-Real-IP HTTP header. Only use if you have a front-end proxy or spoofing may result.” (I have NGINX running on top of Apache). This has fixed all client sites except one (listed), which is now not saving any Wordfence options, including setting auto-updates, IP blocking, setting how WF acquires IPs, restoring defaults; no changes are being saved. I am also unable to scan. Wordfence also loads all of the help popup prompts each time a page loads. I have deleted and reinstalled Wordfence several times, including dropping all WF tables. Cache has been cleared at the server, WordPress and browser levels. Wordfence Assistant is also not saving changes. Please advise.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @brian90069, thanks for your detailed message.

    Your initial action that worked for most sites seems sound and what I’d have suggested. However, the site having trouble saving sounds as if it either has a permissions problem or a plugin conflict. Plugin conflicts can cause our JavaScript to fail so it seems consistent with save operations not working.

    It’s worth checking that in addition to 755 permissions on your WordPress site’s directories, the process owner is also www-data.

    Are you seeing any red errors in the browser console when this occurs? Even if you aren’t, try disabling all other plugins except for Wordfence and see if you’re able to complete the password reset steps. If this works, reenable your plugins one-by-one to see when the issues return. Let us know any errors that you’re seeing with just Wordfence enabled.

    The reason I ask this is because a plugin conflict that’s preventing our JavaScript from working correctly on your pages can appear to be solved when Wordfence is disabled.

    Let me know how you get on!
    Peter.

Viewing 1 replies (of 1 total)
  • The topic ‘Wordfence settings not updating’ is closed to new replies.