I'm trying to re-enable 2FA but now Firefox won't accept any of the generated codes
I'm in the middle of migrating 2FA from Google Authenticator to Authy. Naturally that would involve disabling and reenabling the 2FA setting in my Firefox account. However after scanning the QR code, the Firefox setting keeps refusing ALL the codes generated by Authy. Entering the key manually in Authy also still producing the same error ("Incorrect two-step authentication code").
I have tried searching the help articles here and browsing similar questions by other users but still could not find any working solution (going back to Google Authenticator is not the kind of solution I'm looking for). It seems the problem is with Firefox as the Authy codes never had any problem with other 2FA logins. I hope it's not something like "Firefox does not support Authy". No thanks to that now I'm left with unprotected account.
所有回复 (3)
Did you compare the codes that Google Authenticator generates with the codes Authy generates ?
If the code is wrong then this usually means that Authy doesn't use the correct time and is off that much (more than 30 seconds) that the codes are different.
Can you set in Authy what time server (timezone) to use ?
cor-el said
Did you compare the codes that Google Authenticator generates with the codes Authy generates ? If the code is wrong then this usually means that Authy doesn't use the correct time and is off that much (more than 30 seconds) that the codes are different. Can you set in Authy what time server (timezone) to use ?
Thanks for replying and the suggestion. I tried using the codes from Google Authenticator (which I haven't removed, just in case) and those did not work either.
By the way there is no timezone setting in Authy, as far as I'm aware. That's kind of weird if this "incorrect time" is the cause because like I said Authy has no such problem with other 2FA I'm using it with.
OK I finally found the culprit. It's not the app, it was my computer clock that was out of sync. It was off by 2 minutes. Resyncing the clock with internet time and trying to enter the code again finally works.