2FA not working on GoDaddy. Incorrect “Server Time”

  • Hi there, thanks for a great plugin!

    2FA is currently not working on our site because the “Server Time” and “Wordfence Network Time” listed under Tools > Diagnostics > Time are both incorrect. Interestingly, I can temporarily fix the issue by purging GoDaddy’s server cache. However, this doesn’t fix our main problem because not all users have the capability to purge the cache.

    I imagine I could resolve this issue by excluding the appropriate URL from GoDaddy’s cache. However, I’m not sure what that URL is or how to find it. Can you help?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @solventweb, thanks for getting in touch and I’m glad to hear you’re enjoying the plugin!

    The Wordfence plugin also tries to apply a time offset, based on our one of our server’s timestamps if NTP isn’t available, so I’m surprised that both of these methods might be affected by caching also. If you check Wordfence > Login Security > Settings > General is “NTP” enabled or disabled?

    Also, aside from the Diagnostics page, what values do you see for “Server Time”, “Browser Time” and “Corrected Time” at the bottom of Wordfence > Login Security? If you could paste the output of that here, it’d be very helpful.

    Thanks,
    Peter.

    Thread Starter solventweb

    (@solventweb)

    Hi @wfpeter, thanks for your response.

    Under Wordfence > Login Security > Settings > General, I see the following: “NTP is currently disabled as 3 subsequent attempts have failed.”

    Under Wordfence > Login Security, “Server Time” and “Browser Time” both appear to be correct. I don’t see “Corrected Time” though…

    Server Time: 2023-07-12 22:50:32 UTC (2023-07-12 16:50:32 UTC-6)
    Browser Time:?Wed, 12 Jul 2023 22:50:32 GMT (Wed Jul 12 2023 17:50:32 GMT-0500 (Central Daylight Time))

    Plugin Support wfpeter

    (@wfpeter)

    Hi @solventweb, thanks for your response.

    The corrected time may be missing in this case because the server/browser time matches to the second. Wordfence doesn’t?need?to use NTP for 2FA to work properly as long as the server time is actually correct – which it seems to be from your Server/Browser time output.

    We can try to check for connectivity issues that might be stopping the NTP time, and possibly if there’s anything you can disable in the caching to prevent the purge being necessary for it to work. You can send this information to wftest @ wordfence . com directly using the link at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks again,
    Peter.

    Thread Starter solventweb

    (@solventweb)

    Thanks @wfpeter. Sent.

    Thread Starter solventweb

    (@solventweb)

    Hi @wfpeter, just checking in. Any updates?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘2FA not working on GoDaddy. Incorrect “Server Time”’ is closed to new replies.