• Resolved germars

    (@germars)


    I use Wordfence on 40 to 50 sites and I don’t usually have any issues, but in the past week I’ve had issues with Wordfence either limiting myself or other users to a website. I’ve not made any changes.

    The site I mention above uses s2member to allow members to sign in to private areas and one of them got the 503 message from Wordfence and cannot sign in. I’ve disabled Wordfence for the moment (and on the other site) but I wonder why this is suddenly happening after working for more than a year (on this site) and more on the other.

    And are there any settings I can change to avoid this for myself and other legitimate users? s2member locks out people that try more than 3 times or from different ip addresses.

    Thank you.

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

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support WFAdam

    (@wfadam)

    Hello @germars and thanks for reaching out to us!

    If you check your Wordfence > Tools > Live Traffic, what does it say the block reason is for the users getting the 503? If you could post a screenshot of it, that could help us figure out what is going on.

    Of the 40+ sites, you manage with Wordfence, how many of them run the s2member plugin as well? Just these two that have the issues?

    Thanks!

    Thread Starter germars

    (@germars)

    Hello @wfadam,

    Thank you for your reply. I have a screen shot from the client that signed in. Link below. The other site doesn’t use s2member, and it was just me that was blocked. I just clicked the back button and was able to uninstall wordfence. I’ve tried to turn it on again but it continues to do this.

    For the client that got this page, she got to the sign in page, clicked on her “forgot” password link and created a new password. But when she went to sign in, she got the Site access limited message, she wasn’t able to even get to the sign in page. I looked at the s2member files for her and it didn’t note that she was blocked or that she’d done anything wrong.

    The link to the screenshot is here. https://germars.com/images/wordfence-error.jpeg

    The link to the live traffic for this person is here. https://germars.com/images/wordfence%20live%20traffic.jpg

    And this is the link for the other site without s2member. I can’t get it to stop that Live update thing so the text is greyed out.
    https://germars.com/images/different%20site.jpg

    Thanks for your help.

    Mary

    Plugin Support WFAdam

    (@wfadam)

    Thanks for sending all that information!

    It looks like the user is being blocked for failed login attempts. When the user gets blocked, check your Wordfence > Firewall > Blocking page and filter by “lockout” to see what they are doing that your site might be reading as incorrect.

    Most of the time I see this due to the user having auto-login enabled and the password is incorrect. I would have them try logging in from a different browser.

    Is it just one user having issues?

    Thanks!

    Thread Starter germars

    (@germars)

    Okay, that sounds like a good explanation, but why did another site do the same thing to me while I was signed into the site? I am unable to turn wordfence on again now because I get that error. I’m not having any issues signing in.

    And she said that she thought it was the browser so she tried on a second one as well as her cell phone and then tried again when she got home. All the same error.

    Plugin Support WFAdam

    (@wfadam)

    Does it say anything like “Exceeded Login Attempts” or anything in the Wordfence > Blocking page? I would need to see the reason Wordfence is blocking the IPs.

    It’s strange that it’s blocking her entire account though. That makes it sound like maybe she is using the wrong password or username. I would set her a temporary password and have her use that to test. Preferably in a different browser so auto-login isn’t occurring.

    Let me know how this test goes!

    Thanks!

    Thread Starter germars

    (@germars)

    Hi Adam,

    I’ve already done that for her. I’ve just not turned Wordfence on again to avoid problems again. And there was no notice at all in s2member that she has gone over her limit. What happened was that she changed her password successfully and then was blocked from the sign in page altogether with the notice I sent you. She tried on a couple of different browsers. I have no way of knowing whether it was just her or perhaps the whole group that wasn’t able to sign in, as it’s possible that she’s the only one that tried at that time.

    I’m also wondering why myself, on a different site and while already signed in, also got blocked when I tried to preview a page I was working on. I’ll turn WF back on for both of those sites and see if the issue comes up again and let you know.

    Thread Starter germars

    (@germars)

    Hi again Adam,

    So I was working on the site https://st-pauls-lindsay.ca and when I click on the logout button I get the “you are locked out” page from Wordfence. I’m attaching that message as well as the wordfence Live traffic report.

    I’m the admin, I’m already signed in, I’ve used this plugin for a few years now, why suddenly is it thinking I’m the enemy? I’m also using it at the same IP address, on the same computer. It’s very strange and I’ve had to disable it again.

    https://germars.com/images/wordfence%20live%20traffice%20st%20pauls.jpg

    https://germars.com/images/wordfence-stpauls.jpg

    I hope we can figure out what is going wrong.

    Thank you!

    Mary

    Plugin Support WFAdam

    (@wfadam)

    Thanks for providing that information @germars

    I have seen this happen before when the browser cache is simulating a brute force and then gets the user locked out.

    If you check your Firewall > Blocking page, does it have a reason why it blocked you?

    I recommend purging your cache plugins and clearing your browser cache.

    Let me know what you find!

    Thanks!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Site Access Limited’ is closed to new replies.