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
    Will i be able to access my server if the ezeelogin license server goes down?
    Viewed 1473 times since Wed, Jun 14, 2017
    Class ’DOMDocument’ not found
    Viewed 381 times since Thu, Oct 25, 2018
    Could not connect to database infinite loop on restore
    Viewed 2265 times since Wed, Jun 14, 2017
    vzctl enter veid fails. Unable to get term attr: Invalid argument
    Viewed 1922 times since Wed, Jun 14, 2017
    internal command ezinfo not displaying server details
    Viewed 2202 times since Wed, Jun 14, 2017
    In parallel shell i get "An error occurred. Please contact administrator"
    Viewed 2511 times since Wed, Jun 14, 2017
    LICENSE: No license Please contact [email protected]
    Viewed 1686 times since Wed, Jun 14, 2017
    Error: User add failed. Cannot add user on this node: FAILED: to establish SSH session
    Viewed 543 times since Thu, Sep 6, 2018
    NODE_RDP_PROTOCOL_X224_NEG_FAILURE()
    Viewed 1746 times since Fri, Feb 2, 2018
    ERROR db user: Incorrect datetime value: ’0000-00-00 00:00:00’ for column ’expiry’ at row 1
    Viewed 544 times since Tue, Feb 12, 2019