I was blogging away happily from the Atlanta airport tonight when suddenly MT.Net didn’t like me anymore. I got a message from my Bad Behavior blog spam blocker flagging my IP address. Since I was coming from the airport WiFi’s gateway address, I assumed that spammers and the like may have sent spam from the airport and gotten the address blacklisted. Still, I managed to get in one post from the WiFi before it blocked me, so that didn’t seem to be the right answer.
Checking the Bad Behavior blog tonight reveals the answer:
Within the past two days users have found themselves blocked from their own sites while using recent versions of Bad Behavior. A third party blacklist which Bad Behavior queries recently began sending false positives for any IP address queried, causing everyone using Bad Behavior to be blocked. This issue is fixed in Bad Behavior 2.0.11.
Looks like a spam checker BB checks is providing false-positives. You may find yourself locked out of your own blog until you upgrade to the latest BB, 2.0.11
So there you go. If you’re locked out of your own Bad Behavior-protected blog, you need to install Bad Behavior version 2.0.11 to fix. You can get it here.