Hi @mieche, thanks for reaching out to us.
Even if a username has been guessed or used in a brute force attack after being discovered, I would expect the IP that attempted to access your site unsuccessfully to experience the block rather than the actual user. If the user is experiencing a block, it is possible they are being stopped by configuration issues elsewhere.
From a user-error point of view, you could try ensuring Wordfence > All Options > Brute Force Protection > Immediately lock out invalid usernames is not turned on.
Detecting your server’s IP as a visitor IP by mistake would result in everybody being blocked when one user violates a rule too. To double-check your IP detection is correct, first, check the following site and take note of your IP – (note that this detection can sometimes not be 100% accurate on cellular phone network connections): https://www.whatsmyip.org.
Then, head over to your site and go to Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs and reference the area under that section that says Detected IPs and Your IP with this setting. Start from the top and check to see if any of the settings show that both of those show the same IP as the site above does.
If you’re using Cloudflare, you will most likely need to select “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”.
Let me know if either of those approaches help them with their access!
Do you also have 2FA or reCAPTCHA enabled for administrators?
Thanks,
Peter.
Thread Starter
mieche
(@mieche)
Thanks Peter,
I found the whats my IP site in another thread and had my client send me that info, then white listed the range for her IP and she was able to log in. Hopefully that solves it for now.
There are some definite issues with this site. I inherited it and seem to be playing a constant game of whack a mole as some new random issue pops up randomly.
The site is hosted on GoDaddy and I did read that their caching can sometimes cause problems with Wordfence as well.
During my attempts to problem solve this issue I did turn on the reCAPTCHA. The client does not want to was 2FA yet.