jameshurrell

I confirm that updating to 1.12 has fixed the JavaScript issues.

Amazing service. I confirm that updating to 1.12 has fixed the JavaScript issues.

I’m pleased to report that I’ve now managed to successfully activate 2FA with my wordpress sites! WordFence has updated to v 7.3.3 overnight and the Server Time display is now different, meaning 2FA now works! Hooray, thank you WordFence! Screenshot below:

View post on imgur.com

Thank you, this version seems to fix the 2FA activation issue that I and many others have reported.

I’m pleased to report that I’ve now managed to successfully activate 2FA with my wordpress sites! WordFence has updated to v 7.3.3 overnight and the Server Time display is now different, meaning 2FA now works! Hooray, thank you WordFence! Screenshot below:

View post on imgur.com

I’m pleased to report that I’ve now managed to successfully activate 2FA with my wordpress sites! WordFence has updated to v 7.3.3 overnight and the Server Time display is now different, meaning 2FA now works! Hooray, thank you WordFence! Screenshot below:

View post on imgur.com

• This reply was modified 5 years, 5 months ago by jameshurrell.

Shows that the minority of us that have this issue are not alone…!

Still the same issue. No resolution yet.

Yep, still not working, although no new Wordfence update lately… still on 7.3.2

See also with the same issue:

https://www.ads-software.com/support/topic/2fa-server-time-error/
https://www.ads-software.com/support/topic/error-activating-2fa/

@wfgerald here are some screenshots from my wordpress install:

1) WordPress general timezone settings: https://imgur.com/rpRDlFo
2) Wordfence time: https://imgur.com/gdLKhdT

With this in place, all codes issued from Google Authenticator are rejected when I try to activate.

Edit: I also tried to activate with Authy, and unfortunately that doesn’t work either.

• This reply was modified 5 years, 6 months ago by jameshurrell.
• This reply was modified 5 years, 6 months ago by jameshurrell.

Deleted due to duplicate post

• This reply was modified 5 years, 6 months ago by jameshurrell.

See similar thread here: https://www.ads-software.com/support/topic/2fa-server-time-error/

I had a look in the WordFence plugin files – this is where I think it is getting the time from, right at the end of the file:

wordfence.7.3.1\wordfence\modules\login-security\classes\controller\time.php

I’m not sufficiently good at PHP though to understand what it is doing. It does mention UTC in there though.

I investigated a bit more here. Current situation:

WHM Server time is set to: “Europe/London” and shows correct local time
Wordpress Timezone is set to “London” and shows correct local time
WordFence shows local time minus one hour (UTC) preventing 2FA from working

I then uploaded a test.php file to a cpanel domain containing:

 echo date('Y-m-d G:i:s');
 echo strftime("%c");

Loading this file in a browser showed the time was local time minus one hour (UTC) – OK then something not right here, so I then took a look at my php.ini file and found:

date.timezone = "UTC"

I changed this to:

date.timezone = "Europe/London"

I rebooted WHM and then I reloaded the test.php file. This time the correct local time is showing in the php date output. Yay I thought….

So I then go back into WordPress and check out “Server Time” in the WordFence 2FA section… sadly it is still showing local time minus one hour preventing 2FA from working.

I don’t know where WordFence is picking up the time from….