Hmm, I’m not really sure what’s going on.
So we’ve got Cloudflare Railgun running, could this be a reason? AND we have Jetpack’s Brute force enabled (it was our security solution before Defender. Left it on till we’re sure about Defender) – could this be causing a conflict?
I attempted to lock myself out, but was unsuccessful (attempt 7 failed logins – when the threshold is set to 5 fails – and logged in correctly from that same IP on the 8th attempt).
These unsuccessful attempts weren’t even logged by Defender (let alone block), but Jetpack’s activity log did record these. So I’m thinking a Jetpack – Defender conflict?
Defender is however logging failed logins and blocks against IPs using banned usernames (but not any other username. Though in my test with a banned username, I didn’t get banned).
Also to add to this mix, I just tried a new test – trigger the 404 lockout.
The test:
– On my phone, connected to mobile network (so different IP to my PC), tried to load the page domain.com/include.php and domain.com/include5.php
– /include.php was recorded in the Defender logs, but not the /include5.php
– What’s interesting is the IP. My phone’s current IP address is 82.xxx (UK, where I’m based). Defender logs show the hit as coming from 209.85.238.86 – a Google bot IP.
– On my phone, I used Chrome (on Android) to load the site. But I’m sure Google isn’t supposed to proxy my traffic…are they?!
Maybe I’m just an edge case? :/
[to clarify, the site doesn’t use Google Cloud or Google CDN or anything…so really not sure why a Google IP came up]
p.s. I know I’m not a paying customer yet, so understand that you guys have limited time to try and debug this for me. So no rush.