Blocking All Users from Login

  • Resolved BIrdie

    (@goldendust20)


    7 years, 5 months ago

    We have the premium version of WordFence running, but it keeps causing issues.

    First, the plugin took the site down. An update by the authors fixed this (but yikes, white page for days if the plugin was enabled).

    Second, we were suddenly no longer able to use All-In-One-WP-Migration to take a back up our site. We have to disable the plugin to do so.

    Third, when the plugin is active (even if I deactivate Brute Force protection) the /wp-admin page responds with a WordFence error that we’re temporarily locked out, even though we it was a different browser and a different computer – it’s locking people out of the sign in page, so it doesn’t even know WHO it’s locking out…

    If this is “user error” please let me know what settings we need to adjust to fix this.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • cwongxmatters

    (@cwongxmatters)

    7 years, 5 months ago

    I have a similar issue where if an user gets locked out then all users gets locked, even users who are on different cities, in my case I believe it is because we are using Google Cloud so that makes it look like all users are using the same IP address. Does anyone have any ideas on what the correct setting should be for using Wordfence on a WordPress site that is on Google Cloud?

    wfdave

    (@wfdave)

    7 years, 5 months ago

    Hi @goldendust20,

    I think this might be caused by the blocking rules (which are separate from brute force rules).

    Can you go into Wordfence -> Tools -> Live Traffic, and select a row that has been blocked to see why it was blocked?

    Dave

    WFSupport

    (@wfsupport)

    7 years, 5 months ago

    Hey all –

    @cwongxmatters Just a reminder that the moderators here like you to open your own case, not post in an existing one. Stay tuned though since your problem is probably the same in my first answer. 🙂

    @goldendust20 – As a premium member you have access to support at https://support.wordfence.com if you need it. There’s a bit of faster turnaround since the queue is shorter.

    I’ll answer your questions now though since it may help @cwongxmatters and others out as well.

    • when the plugin is active (even if I deactivate Brute Force protection) the /wp-admin page responds with a Wordfence error that we’re temporarily locked out

      • This sounds like that Wordfence isn’t seeing the correct IPs of visitors. On the Wordfence Dashboard > Global Options page in the General Wordfence Options section look for “How does Wordfence get IPs”. There are 5 different selections there. At the bottom of the section you’ll see “Detected IP(s)” and “Your IP with this setting”. Change the selection until “Your IP with this setting” shows your public facing IP address. See if this helps in your situation. Let us know if not.

    • we were suddenly no longer able to use All-In-One-WP-Migration to take a back up our site. We have to disable the plugin to do so

      • Have you tried putting the firewall into learning mode and then using All-In-One-WP-Migration to take back up? That should whitelist the action going forward so that it isn’t blocked again. If it still happens, then go to Live Traffic and filter for ‘Blocked by Firewall”. Find the entry for the action being blocked and expand it by clicking on it. Take a screenshot and paste a link to it here (In case you don’t already have a place to post it, I love postimage.org for this kind of thing. You can even expire it after a certain amount of time but please don’t make it expire earlier than 7 days so Dave and I get a chance to see it). We may be able to spot the exact rule it is breaking so we can relay that to the QA team.

    • First, the plugin took the site down. An update by the authors fixed this (but yikes, white page for days if the plugin was enabled)

      • Which authors did you mean exactly? The authors of another plugin? The theme? The site? If I were to guess (that’s all I can do at this point) it was either a memory issue, or the last update failed in the middle of the process. If I know more I can be more specific. If you could ask the authors what exactly they did and what date did it happen first it would help.

    Thanks!
    Tim

    cwongxmatters

    (@cwongxmatters)

    7 years, 5 months ago

    @wfsupport Thanks! I was able to resolve my issue! I will post on the new case.

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

The topic ‘Blocking All Users from Login’ is closed to new replies.