• Resolved mddswalk

    (@mddswalk)


    That is the popup message I get when I try to manually block an IP (using Version 6.0.20).

    The alert email includes this info about the IP that is not mine:

    A user with IP address 162.144.100.240 has been locked out from the signing in or using the password recovery form for the following reason: Exceeded the maximum number of login failures which is: 5. The last username they tried to sign in with was: ‘Page’
    User IP: 162.144.100.240
    User hostname: server.katalinagroup.com
    User location: Provo, United States

    I am the only user on the account, “Page” is not my username, and I am not in Provo. The offending user is causing me to get locked out repeatedly. How do I block them permanently?

    https://www.ads-software.com/plugins/wordfence/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WFMattR

    (@wfmattr)

    It sounds like your host is using a “reverse proxy”, so Wordfence cannot see the visitors’ actual IP addresses. You will need to set the option “How does Wordfence get IPs” on the Wordfence Options page. Depending on what software your server is using, you probably need to choose the X-Real-IP or X-Forwarded-For option. More details on the options are here:
    How does Wordfence get IPs

    After setting the option, you can verify it is working by looking at the Live Traffic page, and visiting the site in a separate browser where you are not logged in, and verify that your own IP appears in your own visits. (If Live Traffic is disabled, try logging in using the second browser, since logins and logouts are still recorded.)

    -Matt R

    Thread Starter mddswalk

    (@mddswalk)

    Thanks, Matt R. I chose X-Real-IP (solely because it was the one you listed first) and then checked live traffic from a second browser as you suggested. PERFECT FIX. I was able to manually block the offending user’s IP (292 hits before blocked).

    Thank you. Now I can use Clef without having to first request an unlock email. THANK YOU!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘"An error occurred You can't block your own IP address." It's not my IP address!’ is closed to new replies.