How to Fix Authenticator App Code Not Working for LinkedIn
If your LinkedIn authenticator app code is not working, the problem is usually tied to time drift, a mismatched account entry, or a recently changed security setting.
This guide explains the most common causes and the fastest ways to regain access without locking yourself out further.
Why LinkedIn Authenticator Codes Stop Working
LinkedIn uses time-based one-time passwords (TOTP) for two-factor authentication.
These codes refresh every 30 seconds and must match the secret stored in your authenticator app, such as Google Authenticator, Microsoft Authenticator, Authy, or Duo Mobile.
When a code fails, it usually means one of these issues is present:
- Your phone and LinkedIn are not synchronized to the same time.
- The authenticator entry was added to the wrong LinkedIn account.
- You recently changed or reset your phone and the original secret was not restored.
- LinkedIn’s security settings were updated, invalidating the old code setup.
- You are entering an expired code or mistyping the six-digit number.
Check the Time and Date on Your Device
The most common reason an authenticator code fails is incorrect device time.
TOTP relies on precise timestamps, so even a small difference can make valid codes appear wrong.
What to do
- Set your phone’s date and time to automatic.
- Make sure the correct time zone is selected.
- Restart the authenticator app after changing the settings.
- Generate a fresh LinkedIn code and try again immediately.
On Android, this is usually found under Settings, then Date & time.
On iPhone, check Settings, General, Date & Time, and enable Set Automatically.
If your device has been traveling across time zones or manually adjusted, this step often resolves the issue right away.
Confirm You Are Using the Correct LinkedIn Account Entry
Many users maintain more than one authenticator entry, especially if they manage multiple LinkedIn profiles or previously set up 2FA on another device.
If the authenticator app code is not working for LinkedIn, double-check that the entry you are using matches the exact account currently asking for verification.
Look for clues such as:
- The label attached to the authenticator entry.
- Whether the account was created with a work email or personal email.
- Any duplicate LinkedIn entries in your app.
- Whether you switched phones or restored a backup recently.
If you see multiple LinkedIn codes, try each one carefully.
Do not repeatedly request login codes faster than they expire, because that can create confusion about which token is current.
Make Sure the Code Is Fresh
Authenticator codes expire quickly, so timing matters.
A code that was valid a few seconds ago may already be rejected if you paused too long before submitting it.
Best practices for entering the code
- Wait for a new six-digit code to appear.
- Enter it immediately after it changes.
- Avoid switching apps for too long before submitting.
- Do not add spaces or extra characters.
If your authenticator app shows a countdown ring or time bar, submit the code while plenty of time remains.
If the page reloads or you are routed back to login, generate a new code rather than reusing the old one.
Reinstalling or Changing Phones Can Break Authenticator Access
Authenticator apps do not always restore automatically when you change devices.
Some apps back up codes to the cloud, while others store them locally unless you export or transfer accounts first.
If you replaced your phone, reset it, or reinstalled the app, LinkedIn may still expect the original secret key.
Common scenarios include:
- You changed from Android to iPhone or vice versa.
- You factory reset your phone.
- You deleted the authenticator app and reinstalled it.
- You restored from an incomplete cloud backup.
If that happened, search for a previously trusted device or backup copy of your authenticator setup.
Some apps, like Authy and Microsoft Authenticator, may offer account recovery or cloud sync.
Google Authenticator also supports export and transfer features on newer versions, but only if they were set up before the device change.
Use LinkedIn Backup Codes or Alternate Recovery Methods
If you saved backup codes when you enabled two-factor authentication, use one of them to sign in.
Backup codes are designed for exactly this situation and can bypass the authenticator prompt when the app code is unavailable.
Check for these options on the LinkedIn sign-in screen:
- Backup code entry
- SMS verification, if it was enabled
- Trusted device approval
- Email-based recovery prompts
If you still have access to a logged-in session on another browser or device, go directly to your LinkedIn security settings and review your authentication methods.
You may be able to generate new recovery codes or update your two-step verification settings before the old app is removed.
Update LinkedIn App and Browser Sessions
Outdated app versions or broken browser sessions can interfere with sign-in.
While the authenticator itself is the source of the code, LinkedIn’s login page still needs to accept it correctly.
Try these troubleshooting steps
- Clear your browser cache and cookies.
- Open LinkedIn in a private or incognito window.
- Update the LinkedIn mobile app.
- Try another browser such as Chrome, Safari, Edge, or Firefox.
- Disable VPNs or ad blockers temporarily if they are interfering with login.
Some login failures are caused by a stale session token rather than the authenticator app itself.
A fresh browser session can remove that layer of conflict and allow the code to work normally.
Resync or Recreate the Authenticator Entry
If the code still fails and you still have access to LinkedIn on another trusted device, remove the old authenticator connection and set up a new one.
This is often the cleanest fix after a phone migration or security reset.
Before changing anything, make sure you can complete the full setup process.
In most cases, LinkedIn will show a QR code or setup key that you can scan with your authenticator app.
Afterward, confirm that the new code works before signing out of all devices.
If the old entry is corrupted or duplicated, deleting it from the authenticator app and creating a fresh LinkedIn setup can solve persistent mismatches.
Keep in mind that once you remove the old key, any codes from that entry will stop working permanently.
What to Do If You Are Locked Out of LinkedIn
If you cannot access the authenticator app, backup codes, or another trusted device, use LinkedIn’s account recovery flow.
This may require identity verification, email access, or a government ID depending on the situation and region.
Be prepared to provide:
- The email address or phone number associated with the account.
- Access to the mailbox used for LinkedIn sign-in.
- Any available recovery codes or device confirmations.
- Information that helps verify account ownership.
Do not create repeated new accounts while trying to recover the original one.
That can complicate support handling and may make your login history harder to verify.
How to Prevent LinkedIn Authenticator Problems Later
Once you get back in, strengthen your recovery setup so the issue does not repeat.
A few preventive steps can save time if you ever lose access to your phone again.
- Store backup codes in a secure password manager or offline location.
- Keep automatic date and time enabled on your phone.
- Add a second trusted recovery method if available.
- Use an authenticator app with encrypted cloud backup or export support.
- Review LinkedIn security settings after any device change.
It is also smart to test your recovery options after setup while you still have access.
Confirm that you know where the backup codes are, whether your phone number is current, and whether your authenticator app is backed up properly.
When the Problem Is on LinkedIn’s Side
Occasionally, login issues are caused by temporary LinkedIn service disruptions, browser incompatibilities, or account-level security checks.
If the authenticator code works elsewhere but LinkedIn rejects it, wait a short period and try again from a clean session.
Signs the issue may not be your authenticator app include:
- The code is rejected across multiple devices.
- LinkedIn repeatedly loops you back to sign-in.
- The site displays unusual verification prompts.
- Other users report login problems at the same time.
In those cases, a combination of device time correction, a different browser, and a fresh login session is often enough to clear the error.