• Running a CentOS 7 server on a VPS.

    Checked the server time through ssh shell, checked PHP.ini configuration, checked WordPress General Settings. All display my correct local time.

    When accessing the Login Security/Two-Factor authentication page on the WordPress admin page, the server time displayed at the bottom shows UTC time, which is not the same as displayed in any of the other checks I made. As a result I can’t activate 2fa.

    Please help.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 31 through 40 (of 40 total)
  • Any updates? Still looking for a solution. It is 7 hours difference and 2FA not working…

    I am having this same issue. Unable to activate 2FA. Curiously though, I have two sites on the same server. One functions correctly with no issues with 2FA. Here is the time stamp on the Login Security page:

    Server Time: 2019-10-25 04:03:46 UTC (2019-10-24 23:03:46 UTC-5)
    Browser Time: Fri, 25 Oct 2019 04:03:59 GMT (Fri Oct 25 2019 00:03:59 GMT-0400 (Eastern Daylight Time))
    Corrected Time (WF): 2019-10-25 04:03:57 UTC (2019-10-24 23:03:57 UTC-5)

    On the site where 2FA is not functioning (remember, same server) here is the time stamp:

    Server Time: 2019-10-25 04:02:27 UTC (2019-10-25 00:02:27 America/Toronto)
    Browser Time: Fri, 25 Oct 2019 04:02:39 GMT (Fri Oct 25 2019 00:02:39 GMT-0400 (Eastern Daylight Time))
    Corrected Time (WF): 2019-10-25 04:02:38 UTC (2019-10-25 00:02:38 America/Toronto)

    So I went to settings and rather than set it to Toronto, where I am, I set it to UTC-4 and then the time was correct. However, 2FA STILL would not activate.

    And the other curious thing is that 2FA WAS working previously but then all of a sudden, I would try to log in and get a warning that I had to enter my security code when required but that request never showed up.

    Something definitely amiss.
    Dave

    punkum

    (@punkum)

    I’m not having any success either.

    Server Time: 2019-11-12 00:43:55 UTC (2019-11-12 11:43:55 Australia/Sydney)
    Browser Time: Tue, 12 Nov 2019 00:43:58 GMT (Tue Nov 12 2019 11:43:58 GMT+1100 (Australian Eastern Daylight Time))

    Getting code via my mobile phone and the Symantec VIP Access code generator app.

    Just keeps saying wrong code, check server time.

    Hi, I experienced the same issue. I solved it by synchronising (“synchronise now”) the authentication app instead of looking for a solution in my wordpress time settings.
    Bart

    Same problem…using latest Wordfence (7.4.6)and WP. Also confirmed in Wordfence Tools Diagnostics that times all match +/- 1 sec.

    Any solutions yet?

    Also having this problem. Using Wordfence 7.4.7. which shows server time as UTC in 2FA, while local time in the Netherlands is UTC+2.

    Anybody from Wordfence in this forum who can help us?

    I am having this problem also. I’m using Authy and it works fine on three other (non-Wordpress/Wordfence) sites I am administering. Those sites are running xenforo forum software so I can only think the issue is with Wordfence.

    My WordPress Time settings are correctly set to my location (London). It would seem that xenForo is correctly reading the Server time (which is London) , while Wordfence is incorrectly reading the server time.

    I’m having this problem too. I use Google authenticator – this is fine logging in to the site with Plesk but not on the WordPress side..

    Server Time: 2020-07-14 19:52:30 UTC (2020-07-14 20:52:30 Europe/London)
    Browser Time: Tue, 14 Jul 2020 19:52:31 GMT (Tue Jul 14 2020 20:52:31 GMT+0100 (BST))

    I believe this may be the solution:

    After making timezone changes to the Settings -> General -> Timezone and saving those changes, I deleted the existing entry in my Google Authenticator app and then rescanned the QR barcode.

    It’s working now.

    I first synchronized the authenticator, then I rescanned and replaced it in the authenticator app. Now it’s working.

Viewing 10 replies - 31 through 40 (of 40 total)
  • The topic ‘2fa Server Time Error’ is closed to new replies.