2FA not working because of time offset

  • Resolved prool

    (@prool)


    4 years, 6 months ago

    Hello, here are my values from tools/diagnostics/time/

    Time Server time accuracy and applied offsets.
    Wordfence Network Time: 2020-05-08 02:14:59 UTC
    Server Time: 2020-05-08 02:14:59 UTC
    Wordfence Network Time Offset – 9 minutes 40 seconds
    NTP Time Offset + less than 1 second
    TOTP Time Source: Wordfence Network
    WordPress Time Zone: Europe/Berlin

    What i really do not understand, why the time source is “Wordfence Network”, on all other websites where i use wordfence, the TOTP Time Source is “Server Time”. Is this the cause of the problem? what can i do?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter prool

    (@prool)

    Now it works again, the wordfence network offset was reduced in the meanwhile

    This information i found under “Login Security” at the buttom:
    Server Time: 2020-05-08 02:30:04 UTC (2020-05-08 04:30:04 Europe/Berlin)
    Browser Time: Fri, 08 May 2020 02:30:06 GMT (Fri May 08 2020 04:30:06 GMT+0200 (Mitteleurop?ische Sommerzeit))
    Corrected Time (WF): 2020-05-08 02:30:03 UTC (2020-05-08 04:30:03 Europe/Berlin)

    Was this error on your end? And the Question remais, why is the wordfence plugin on this installation using TOTP Time Source “Wordfence Network” instead of “Server Time”.

    • This reply was modified 4 years, 6 months ago by prool.

    Hi @prool,

    Wordfence can choose between these TOTP Time Sources:

    – NTP
    – Wordfence Network
    – Server Time

    If NTP time fails, it uses Wordfence Network, and if that fails, it uses Server Time.
    I wouldn’t recommend manually setting the time source to server time – your server should automatically sync up again so that the time matches correctly.

    Please let us know if it becomes out of sync again.

    Dave

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘2FA not working because of time offset’ is closed to new replies.

Tags