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
    Unable to login into cpanel/whm with one click
    Viewed 5664 times since Wed, Jun 14, 2017
    Class ’DOMDocument’ not found
    Viewed 634 times since Thu, Oct 25, 2018
    main admin user account suspended after entering incorrect security code
    Viewed 2638 times since Wed, Jun 14, 2017
    How do i disable google 2 factor authentication or other 2factor mechanisms?
    Viewed 4411 times since Wed, Jun 14, 2017
    getting config from other node failed
    Viewed 565 times since Wed, Jan 9, 2019
    The IP field must contain a valid public IP or how to install Ezeelogin on a machine in lan
    Viewed 3308 times since Wed, Jun 14, 2017
    Jump server ip to be licensed?
    Viewed 2502 times since Thu, Jun 15, 2017
    NODE_RDP_PROTOCOL_X224_NEG_FAILURE()
    Viewed 2682 times since Fri, Feb 2, 2018
    Connection has been closed. Another user may have logged in on the remote windows machine
    Viewed 2649 times since Thu, Jun 15, 2017
    User add failed: Error waiting for connection: Cannot add user on this node: Could not connect
    Viewed 1988 times since Wed, Jun 14, 2017