-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Failed to create a login nonce' notification #501
Comments
Correct, but no response in either place... :P |
I haven't been able to replicate this with plugin version 0.7.3 and WP 6.1.1. @mikolajek Which of the two-factor methods do you have enabled and which one is selected as the default? |
There are three code paths where this error message is returned: two-factor/class-two-factor-core.php Lines 549 to 552 in b67c7da
two-factor/class-two-factor-core.php Lines 896 to 904 in b67c7da
two-factor/class-two-factor-core.php Lines 906 to 917 in b67c7da
|
Thanks, @kasparsd! I use Yubikey as the default method and emailed OTP as the backup one. A question - does this plugin puts any references to other code? I mean if I remove it via FTP, do I have to make any other changes in my WP? |
No, renaming the plugin folder would've completely removed the plugin from the system. This issue sounds like an issue of using an Object Cache, PHP Code cache, and/or cookie problem.. @mikolajek Did you find anything to resolve this? I'm tempted to close this issue unless some more information can be provided. |
Hi there, today, out of the blue, my site with Two-Factor 0.7.3 installed started to display the "Failed to create a login nonce" notification. I'm running WP 6.1.1 and it seems to me the latest WP upgrade (6.1 => 6.1.1) might have caused this, as I made no changes to the config myself.
I disabled the plugin by renaming its folder, but in this case, I can't log in either. The login screen just keeps refreshing and gets back to the credentials screen. Is there a way to disable the plugin and get to the WP admin screen?
BTW - I have no cache plugin and clearing just the browser cache doesn't work...
The text was updated successfully, but these errors were encountered: