Hi @whaleman, thanks for getting in touch.
That’s behavior I’ve not seen before although initially looked similar to an alternate way users can log in with 2FA (by appending it manually to the end of the password). Firstly, I would ensure auto-fillers like password managers, other browser plugins, and local caches aren’t involved by getting the user to try again in a different browser, or a private/incognito window with browser extensions disabled. If it works, it’s not caused at your site’s end.
We generally only recommend having Wordfence > All Options > Brute Force Protection > Immediately lock out invalid usernames checked if you’re the sole administrator. If you have an online store or other reason for a number of external users, simple typing errors will result in blocking legitimate users quite frequently. Of course, this is an unusual case but you could temporarily disable that and let us know if the user is told their username is invalid once the code is appended to the end.
Let us know what you find out,
Peter.
Hi Peter,
As you suspected the Brute Force Protection was turned on to immediately lock out any invalid user names. I turned this off and asked my colleague to try again. This time it worked for her, she was able to log in with 2FA and all seems fine.
I’m not sure why she was the only person to have this issue but will keep the setting turned off as you suggested as we many users regularly logging into the site.
Many thanks for your help.
George