Google 2 factor authentication fails randomly

Google 2 factor authentication does not work all the time

 The server time is incorrect. The time on the server needs to be synchronized with a time server. Even, if the time on the server has an offset of 5-10 seconds, the google 2factor authentication would have random failures.

 Use the command to correct the server time.

ntpdate pool.ntp.org

Also, do ensure the time on your mobile phone is correct as well. Sync the time on your mobile with that your mobile operator to ensure that time is accurate.

The battery on the motherboard could be weak or failing which may cause the server time to fall behind a few seconds. Its recommended to keep the above command added as a cronjob.

5 (1)
Article Rating (1 Votes)
Rate this article
    Attached Files
    There are no attachments for this article.
    Related Articles RSS Feed
    getting config from other node failed
    Viewed 432 times since Wed, Jan 9, 2019
    Configuration and error log files to check for troubleshooting
    Viewed 4005 times since Thu, Jun 15, 2017
    Disable two factor authentication (2FA Google, Yubikey , Access Keyword, DUO)
    Viewed 5601 times since Thu, Jun 15, 2017
    Why does the ssh log have control characters and looks different from the actual input?
    Viewed 1904 times since Thu, Jun 15, 2017
    vzctl enter veid fails. Unable to get term attr: Invalid argument
    Viewed 2208 times since Wed, Jun 14, 2017
    Could not setup Ezeelogin Web SSH service
    Viewed 1920 times since Sat, Nov 18, 2017
    Internal command ezinfo or ezlist does not work even though i am in the admins group.
    Viewed 2505 times since Thu, Nov 23, 2017
    LDAP verification failed. Connection to {hostname} closed.
    Viewed 787 times since Fri, May 18, 2018
    Blank page when clicking add server
    Viewed 1681 times since Wed, Aug 16, 2017
    Could not setup Ezeelogin Web SSH service in ssh jumphost
    Viewed 888 times since Fri, Feb 16, 2018