This guide has the answers to common error cases that we see.
I lost my TOTP device
I lost my hardware token
I can't find my recovery codes
My MFA tokens aren't working--why is it now asking me for two?
It's not accepting my TOTP token to enable MFA
If you do not see your issue, please contact us through the built-in chat, or email us at hello@dispel.io. We are actively here to help you!
I lost my TOTP device
Log into your account with a recovery code, or with a hardware token if you have that in addition to TOTP.
I lost my hardware token
Log into your account with a recovery code, or with another form of MFA if you had multiple.
Obtain a new hardware token (sorry, we can't help with that)
Add your new hardware token, like this if that was your only MFA.
I can't find my recovery codes
Figure out a safe place to store your new recovery codes.
My TOTP tokens aren't working--why is it now asking me for two?
To prevent brute force attacks, if you use the wrong token enough times in a row, we will start asking for two.
If you are not a malicious actor and this is actually your account, log in with a recovery code, disable your TOTP, and re-enable it.
My TOTP token is getting rejected while I'm trying to enable MFA
If you are failing to enroll due to the generated code being rejected it is possible that the time on your 2FA-device is not synced properly. This is due to the codes being time based. We recommend visiting https://time.is and attempting to verify whether the time on the 2FA-device which is generating the codes is synced properly. If it is not synced please follow the steps outlined here: https://squareup.com/help/us/en/article/5288-update-date-time-on-your-device