Troubleshooting
Two-Factor Authentication Is Blocking Your Login
Codes aren't arriving or aren't working, and you can't get past the two-factor screen.
Is this your situation?
You turned on two-factor authentication and now the code screen won't let you through. The device you expected to use for the recovery code isn't available to you.
The short answer
Two-factor authentication asks for a code each time an unrecognized browser or device tries to log in. If a text message code is delayed, check your phone again after a few minutes. If none of the SMS, approve-login, or recovery code tips work, you can ask Facebook to confirm your identity to regain access.
What you see, and why
| Symptom | Cause |
|---|---|
| The SMS code never arrives. | Text message codes can sometimes be delayed by the mobile carrier. |
| You entered the code but login still fails. | The authentication screen asks for a code each time you log in from an unrecognized device or browser. |
| You don't have your phone at all. | You can look for an option that says I don't have my phone on the authentication screen. |
| None of the options on screen work. | You can ask Facebook to confirm your identity to regain access. |
Check these first
- Check another logged-in device You can approve a login attempt from a different browser, phone, or tablet already logged in.Verify: A prompt to approve a new login attempt may appear on that device, without needing a code.
- Check for a saved recovery code Recovery codes are one-time backup codes generated from Security and Login Settings.Verify: Look for a printed or saved list of codes.
- Check your phone again after a few minutes SMS codes can be delayed by the carrier.Verify: Check whether the code has arrived yet.
How Facebook handles this
- Two-factor authentication requires entering a code in addition to your password when logging in from an unrecognized device or browser.
- A recovery code can be entered in place of the two-factor authentication code to log in.
- Meta recommends keeping two-factor authentication turned on to protect the account.
- If none of the SMS, approve-login, or recovery code options work, you can ask Facebook to confirm your identity.
Which path applies to you?
- Is another device already logged into your account? You can approve the login attempt from that device without entering a code.
- Do you have saved recovery codes? You can enter a saved recovery code in place of the two-factor code to log in.
- Is the SMS code delayed? Check your phone again after a few minutes.
- Do you have no access to your phone at all? Look for the option that says I don't have my phone on the authentication screen.
- Did none of the above work? Ask Facebook to confirm your identity to regain access.
Step by step: finding the cause
- Wait for a delayed SMS code Carriers can delay codes.Where: Login → Login code screenConfirm: Check your phone again after a few minutes.
- Try approving from another device You can approve a login attempt from another device if already logged in on a different browser, phone, or tablet.Where: Login → Another logged-in deviceConfirm: Look for a prompt to approve the login.
- Enter a recovery code instead A saved recovery code can be entered in place of the code to log in.Where: Login → Login code screenConfirm: Check that the recovery code field accepts it.If this fails: Each recovery code only works once.
- Select 'no phone' option If you lack phone access, look for I don't have my phone on the screen.Where: Authentication screen → I don't have my phoneConfirm: Look for the I don't have my phone option.
- Start identity confirmation On a computer, click Need another way to authenticate?, then Other Options, then Get more help.Where: Login → Login code screenConfirm: Check that Get more help opens identity confirmation.
- Submit identity confirmation This may involve uploading a photo of a government-issued ID, such as a driver's license or passport.Where: Login → Identity confirmation screenConfirm: Check that your submission was accepted.
Common mistakes
- Using private browsing Private browsing usually causes a security code request after closing the browser window.Why it happens: Some web browser features block Facebook from remembering the computer and browser information.
- Clearing browser history on close Clearing history every time the browser closes can require a code each login.Why it happens: Facebook needs to remember your computer and browser information to recognize it next time.
- Trying identity confirmation on Facebook Lite Identity confirmation isn't available on Facebook Lite.Why it happens: Facebook Lite doesn't support the identity confirmation steps.Already happened: Open the full Facebook app for Android or visit www.facebook.com in a browser instead.
- Expecting one-time passwords to work One-time passwords aren't available if two-factor authentication is turned on.Why it happens: One-time passwords are not available if two-factor authentication is turned on.
Quick reference
| Situation | What to do |
|---|---|
| SMS code delayed | Wait a few minutes and check again. |
| Another device logged in | Approve the login attempt there. |
| Have recovery codes saved | Enter one in place of the two-factor code. |
| No phone access | Select the no-phone option on screen. |
| Private browsing in use | Expect to be asked for a code each login. |
| All options exhausted | Ask Facebook to confirm your identity. |
| Using Facebook Lite | Open the full Facebook app to complete identity confirmation. |
Keeping track of who has access
Delvia helps you keep account access organized once you've diagnosed what's blocking your login.
Was this helpful?