@ravi923615 I also had this just now. I logged into hosting and renamed the wordfence plugin with -old at the end and was able to log in. I’ve tried to disable 2FA but it refuses to let me. I read somewhere on an old thread that might be the problem.
@ravi923615 If you can log back in and rename the wordfence folder back to wordfence again you should be able to look in live traffic for your IP address and see the reason you were locked out.
@iguanamom Renaming the Wordfence folder would also deactivate the 2FA that Wordfence provides in the plugin. If you have the site in Wordfence Central, our free site management tool on Wordfence.com (read more about it here) you could add your public facing IP address to the allowlist that bypasses 2FA. You can read more about Wordfence Central here:
https://www.wordfence.com/help/central/
If you have further questions, please open your own support thread so we can better track issues.
Tim
FWIW, I had to do a restore back to the 19th. I was also having issues with WooCommerce and I see that’s one plugin that now needs updating (the cart payment section was constantly spinning). As the files were restoring, I was still not able to log back into the site without that message appearing. Now that all files have restored, I no longer get that message and logged in ok and cart is fine too. So if you had updated WooCommerce, you may want to restore and test this out in staging. Sorry for the blame here, Wordfence!!
@iguanamom Thanks for your suggestion, Appreciate it. @wfsupport Haven’t tried anything since I had the rule for blocking set to 1 day, It got unlocked after one day but there wasn’t any incorrect login attempt from my IP Address. So, it was strange that it got locked out itself.