Page MenuHomePhabricator

Reset 2FA for User:There'sNoTime
Closed, InvalidPublic

Description

TNT approached me on IRC saying that "apparently the codes [Google Authenticator] is now generating are invalid, which means I can't log into phab either." Can provide screenshots if needed, see also proof onwiki

He is logged in on his home PC and work laptop.

Event Timeline

As There'sNoTime's confirmed alt I can confirm the above - it appears other users have also been having issues with TOTP clients supplying invalid tokens/WP not accepting valid tokens.

I'm logged in on my home PC and a work laptop, but can't log in on new machines as the verification code section has error Verification failed. on entering a Google Auth generated code.

I'd like 2FA disabled on the account so I can try setting it up again with Google Auth.

I didn't take a copy of the scratch codes.

I didn't take a copy of the scratch codes.

You should fix that.. Especially as right now, there is no way to ever retrieve your account if you loose your phone...

@TheDJ not my finest moment, as I actually was a rather outspoken advocate of 2FA being introduced and wrote the English Wikipedia guides on using it..

TNTPublic claimed this task.

Self-close, time correction had not been synced in Google Auth. Leaving T168064 open

For the future, the fix for this is:

Google Authenticator --> Settings --> Time correction for codes --> Sync now

Aklapper changed the task status from Resolved to Invalid.Jun 16 2017, 2:30 PM

No 2FA reset happened, hence closing as invalid