Locked Out

Same here. Single login attempt and I am getting “forbidden” in /wp-login.php, even though my IP is whitelisted.

Have you updated to version 4.2.8 ?
May be you can report this bug with more details in the link that you can find in the third sticky thread on this support forum.

@cheryl-k
like i was telling nadworks, may be you have to clean up some files… have a look at this thread “Continuous LOCKOUTS cannot do anything!!!! Backup problems too!!“.
Let us know with more details…

best regards.

L..

@nadworks forbidden means you’ve tripped the permanent blacklist feature. It sounds like you might have a lot of 404 errors from missing images or other items. I would recommend turning off 404 detection until you can fix those and remember that if my plugin is seeing them so is Google and other search engines. In the meantime you’ll have to manually remove your ip from .htaccess. As for the whitelist part, if that still doesn’t work for you contact me directly and we’ll get to the bottom of it (it isn’t hard to find me, just google my name).

@cheryl-k sounds like someone else is trying to log into your site as you. You can clear it via iThemes Sync or log in as a second user name. When you do get in make sure to change your username. This is actually what the plugin should do. It sucks that you can’t get in but it makes sure whomever is trying your account can’t get in either. In the future if you have a permanent IP address you can add it to the whitelist and the username lockout won’t affect your computer.

Thanks, Chris – just to resolve the issue I had: It had nothing to do with iThemes Security in the end. It turned out that the combination of my site using CloudFlare and my web host having their own security in place, the static IP generated by CloudFlare was permanently blocked on the host server.

This was fixed by using the iTheme Security login link redirect, to avoid going through the standard wp-login.php. I had used this feature before, but had disabled it recently for various reasons.

Took me a long time to figure out, but eventually got clarification from my host about what the lockout cause was. All fine again.