Odd Brute force protection message

  • Resolved themps

    (@themps)


    8 years, 7 months ago

    I have a user that just recently started having trouble logging in. It says IP 173.245.55.217 is blocked. However that is not their IP at all. And I’ve confirmed it isn’t and white listed their actual IP. Any attempt at the admin section and they receive that error. It also seems to be new since the last update. They have an admin account. I also have an admin account and am not having the same issue. Andy ideas? I’ve had to disable it for now.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter themps

    (@themps)

    this almost looks like an internal Jetpack IP. Did brute protect flag one of jetpack’s IPs?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    It says IP 173.245.55.217 is blocked.

    This appears to be a CloudFlare IP address.

    Could you contact us via this form, and give us as many details about your site and CLoudFlare setup as possible, so we can look into this and try to understand why that user appears as using a CloudFlare IP when logging in to your site.

    Thanks!

    Thread Starter themps

    (@themps)

    Ah ok yes I do use cloudflare. I’ll send in my details. Thanks!

    Thread Starter themps

    (@themps)

    i did submit the ticket 2 days ago….do you suppose it would be safe to whitelist that IP for now? I mean the odds of a brute attack from that particular IP on my site would be fairly low right?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    i did submit the ticket 2 days ago…

    We’ll reply to you soon!

    do you suppose it would be safe to whitelist that IP for now?

    Yes, you could whitelist that IP, but at this point, if Protect doesn’t detect the right IP when you try to log in, it might be best to deactivate the Protect module altogether, since it clearly doesn’t work well on your site at the moment.

    Thread Starter themps

    (@themps)

    Thanks Jeremy and Richard. They made an internal change and it’s working fine now.

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Odd Brute force protection message’ is closed to new replies.