![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Security code for 2FA is not working
Since I bought a new phone, I was trying to login to my account for Firefox on that device too. I was not sure where to find my recovery codes for 2FA, so after a lot of messing around, I've disabled 2FA and was able to login on my new smartphone without it.
Now I'm trying to setup 2FA again, following the steps as described in the Support article: https://support.mozilla.org/en-US/kb/secure-firefox-account-two-step-authentication
However, when I scan the QR code with either Google Authenticator or Authy (which I tried, because I thought Google Authenticator was not returning a working security code), the 2FA setup keeps telling me the code is not right. What am I missing here?
In Google Authenticator I've already tried the "Time correction for codes" setting (my app is in Dutch, so I guess that's what the setting is called), but that also didn't help. I tried logging out and in again on my laptop, also doesn't work.
Any ideas/suggestions?
所有回复 (2)
If you used Google Authenticator on the old device and still have access then you can transfer its settings to the new device, but since you already have done a disabled/enabled sequence that won't help you now. Issues with the security code not working as most likely caused by issues with the (internet) time service used on that new device or on your desktop computer as the code in only valid for thirty seconds, so if the generated code is already near the end of its validity then best is to wait for the next code update.
@cor-el My old phone died on my, I'm afraid. But as you already said, I have already done the disable/enable for 2FA.
I've tried everything with the Google Authenticator app already. I'm well in time before the code expires with entering the code and submitting the form, I've already did the Time Correction setting for Google Authenticator and even with Authy I've tried it multiple times, all well within the timeframe before the security code expires. So that can't be the issue here.