Totp Not Working

[Ken]

Suddenly TOTP w/ Google Authenticator is not working.  Nothing has been changed between the time it worked and didn't work.  I disabled through the database and so far I have:

 

1. Re-Enabled TOTP via Admin login

2. Fresh install of Google Authenticator on another device

3. Updated from 3.0.6 to 3.0.7

 

Each time gives an error at the OTP input screen during login:  The one-time password entered is invalid.

 

Is anyone experiencing this issue?

[velaware]

TOTP is based on time, so if the time is desynched (which isn't uncommon) it will cause TOTP to fail in certain situations.

 

Log in to your server (not Blesta but the actual server) and run ntpdate pool.ntp.org to update your time.

[Cody]

The time between the device and server must be less than +/- 3 minutes of each other.

[Ken]

TOTP is based on time, so if the time is desynched (which isn't uncommon) it will cause TOTP to fail in certain situations.

 

Log in to your server (not Blesta but the actual server) and run ntpdate pool.ntp.org to update your time.

 

That would be the problem!

[Paul]

We recommend setting up ntpd to keep sync'd up with a time server. On RHEL/CentOS this should work..

yum install system-config-date
ntpdate pool.ntp.org
chkconfig ntpd on
service ntpd start