Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Unable to activate/reactivate 2FA, keep getting "Incorrect two-step authentication code" message.

  • 4 ответа
  • 8 имеют эту проблему
  • 16 просмотров
  • Последний ответ от JibeddyHibeddy

more options

Hello,

I had to deactivate 2FA briefly, and then attempted to use a reactivate it again. I am able to scan a QR, but when I try to enter the OTP codes that show up, I receive the following message "Incorrect two-step authentication code". This has happened with Raivo and Authy (the previous 2FA app). What is causing this?

Hello, I had to deactivate 2FA briefly, and then attempted to use a reactivate it again. I am able to scan a QR, but when I try to enter the OTP codes that show up, I receive the following message "Incorrect two-step authentication code". This has happened with Raivo and Authy (the previous 2FA app). What is causing this?

Все ответы (4)

more options

Make sure the date/time/timezone on all devices is correct and is synced to a reliable internet service as the TOTP code is only valid for thirty seconds. You can try to enter the otpauth:// directly in the app instead of using the QR code.

more options

Hello,

The time/date/timezone are correct, and I have tried doing it manually, but still no luck. Whatever I do, I still receive the following message: "Incorrect two-step authentication code".

more options

I´m actually facing the same problem. I tried to activate 2FA for the first time for Firefox using Authy on iOS, but whatever I do, I get the same error message, saying that the code I entered was wrong. I also even manually added the token instead of scanning the QR code, but it didn´t help. All my devices are setup for the same timezone and show the same time, so I could rule this out, too.

Best regards, Tobias

more options

I was also experiencing this problem just now. You can workaround it by using a mobile browser on your phone, but it's a bit silly this still hasn't been resolved.