(EDIT: Nevermind, Issue resolved – I removed the site from the Authenticator app, re-added it, and now it is working.)
Thank you for adding these features to the free version of the plugin.
I am still getting this error.
On the site: The server time is correct as reported in the Wordfence>Tools>Diagnostics page.
On my mobile: I have run Google Authenticator > Time correction for codes, and the result is “Time already correct”
I’m assuming it doesn’t matter that I’m in a different time zone from the server.
What else can I try?
I’m seeing server time error. Diagnostics times match to within one second.
Server Time: 2019-09-01 10:49:06 UTC (2019-09-01 22:49:06 Pacific/Auckland)
Browser Time: Sun, 01 Sep 2019 10:49:07 GMT (Sun Sep 01 2019 22:49:07 GMT+1200 (New Zealand Standard Time))
This is driving me crazy. FWIW I had the same experience with another 2fa app.
Wordfence:
Server Time: 2019-09-08 04:52:25 UTC (2019-09-08 16:52:25 Pacific/Auckland)
Browser Time: Sun, 08 Sep 2019 04:52:27 GMT (Sun Sep 08 2019 16:52:27 GMT+1200 (New Zealand Standard Time))
WP General:
Universal time (UTC) is 2019-09-08 04:52:27. Local time is 2019-09-08 16:52:27.
PHP my info:
hello world
2019-09-08 16:52:28
-
This reply was modified 6 years, 7 months ago by
square_eyes.
-
This reply was modified 6 years, 7 months ago by square_eyes.
Not resolved, still broken.
Server Time: 2019-10-01 16:44:17 UTC (2019-10-01 18:44:17 Europe/Berlin)
Browser Time: Tue, 01 Oct 2019 16:44:16 GMT (Tue Oct 01 2019 18:44:16 GMT+0200 (Central European Summer Time))
Will not accept my 2FA
I had the same issue, I set the timezone in WP to my own, and then was able to activate 2FA, after that I set the real timezone back and now I’m unable to login. I am in Europe, Server is in America. How can I get around this without faking my timezone?
Could this depend on the App I’m using (LastPass)?
Hi I have the same problem
The settings in Wordfence > Tools > Diagnostics > Time are
Time Server time accuracy and applied offsets.
Wordfence Network Time
2019-12-18 13:37:45 UTC
Server Time
2019-12-18 13:37:45 UTC
Wordfence Network Time Offset
+ less than 1 second
NTP Time Offset
Blocked
TOTP Time Source
Server Time
WordPress Time Zone
Europe/Rome
Thanks for your help
-
This reply was modified 6 years, 4 months ago by
applina.
Nothing I do fixes this same error.
2020-01-15 22:48:55 UTC
Server Time
2020-01-15 22:48:55 UTC
Wordfence Network Time Offset
+ less than 1 second
NTP Time Offset
Blocked
TOTP Time Source
Server Time
WordPress Time Zone
America/New_York
We are seeing the same issue. Didn’t happen when enabling 2Fa for all admins months ago. But now, when adding my first editor, she is having and I am having (as the admin witness) this issue. The time on her phone is the same as the time on my phone, and I am successful in my logging in. She is unsuccessful in the activation. She has an iPhone with the Duo app. I have an android with the duo app.
My local time on my phone and server time are set to BST (UTC + 1). The website is for a company who are based in a different time zone AZOTS (UTC + 0). I have tried setting the WP Timezone to UTC-1, UTC+0, UTC+1 & Azores and I still get:
The code provided does not match the expected value. Please verify that the time on your authenticator device is correct and that this server’s time is correct. So they are both correct but in different timezones. How do I activate 2FA?
Why does the display on the 2FA page say Server Time – it’s not, it’s the WordPress Timezone?
Still doesn’t work for me.
Time at all 3 places (WF Diagonostics, WP Settings and on the Authenticator device) match but it still doesn’t work for me.
This issue started a few weeks back for me.
Hey, I have the same issue.
In Wordfence, the server time and the network time are different.
The wordfence server time is different than the wordpress time.
Any idea?
Thank you!
