How to Fix 1Password Authenticator Code Not Working in 2026
If you rely on 1Password for two-factor authentication, a broken code can lock you out at the worst possible moment.
This guide explains the most common causes and the exact steps to get your authenticator codes working again.
Why 1Password Authenticator Codes Stop Working
Authenticator codes in 1Password are time-based one-time passwords, or TOTP codes, generated from a secret key stored in the vault.
The code changes every 30 seconds and must stay closely synced with the server accepting it.
When the code fails, the issue is usually not 1Password itself.
Common causes include incorrect device time, a bad scan of the QR code, stale vault data, an expired login session, or a service that no longer accepts the old two-factor method.
Check Your Device Time First
The most common reason for how to fix 1Password authenticator code not working is clock drift.
Even a small difference between your phone or computer time and the server time can make a TOTP code invalid.
- Enable automatic date and time on your device.
- Turn on automatic time zone detection if available.
- Restart the device after changing time settings.
- Try generating a fresh code after the clock resyncs.
On iPhone and Android, time settings are usually found in the system settings under Date & Time.
On Windows and macOS, confirm that network time is enabled and the time zone is correct.
Verify That the Correct Login Item Is Selected
Many users store multiple entries for the same website, especially if they have personal and work accounts.
If you open the wrong 1Password item, you may be copying a code tied to a different account.
- Search the exact domain name of the service.
- Compare the username or email address.
- Check whether the item contains multiple one-time password fields.
- Make sure you are using the code for the account currently asking for verification.
This issue is common with shared family vaults, duplicated logins, and imported passwords from another password manager such as LastPass or Bitwarden.
Rescan the QR Code or Re-enter the Secret Key
If the authenticator setup was incomplete or the QR code was scanned incorrectly, 1Password may generate codes that the service rejects.
This can happen during initial enrollment or after re-adding an account on a new device.
To fix this, remove the existing authenticator entry from the item and set it up again using the service’s two-factor setup page.
If the QR code is unavailable, use the manual secret key instead, and paste it carefully without extra spaces.
- Prefer the official QR code from the service’s security settings.
- Use manual entry only if QR scanning fails.
- Confirm the issuer, account name, and secret are entered exactly.
- Save the item and test the newly generated code immediately.
Make Sure 1Password Is Fully Synced
Because 1Password syncs vault data across devices, an outdated copy of a login item can show the wrong authenticator secret.
This is especially likely if you recently changed devices, restored from backup, or edited the item on another platform.
Open 1Password on each device and confirm that sync is complete.
If the app appears stuck, sign out and sign back in, or force a manual sync if your 1Password version offers it.
On the web, refresh the browser and check that you are logged into the correct account.
If the code works on one device but not another, the problem is usually vault mismatch rather than the authenticator algorithm itself.
Check Whether the Service Requires a New 2FA Setup
Some websites and apps rotate or invalidate two-factor authentication secrets after password changes, account recovery, or security resets.
In those cases, the old 1Password code will never work again because the service has already issued a new secret.
Review the account’s security settings on the service you are trying to access.
If two-factor authentication was reset, remove the old entry from 1Password and enroll again with the newly issued QR code or backup secret.
- Password changes can trigger 2FA resets on some platforms.
- Account recovery may disable the previous authenticator secret.
- Admin-managed business accounts may enforce fresh enrollment.
- Security policy updates can invalidate old TOTPs.
Confirm You Are Copying the Code at the Right Time
TOTP codes expire quickly, so timing matters.
If you copy a code too early, wait too long, or submit it as it changes, the service may reject it even though the code looked correct when copied.
Open the code only when you are ready to paste it, and submit it immediately.
If the service supports it, enter the current code manually instead of reusing an old clipboard value.
This matters most on slow connections, mobile browsers, and remote desktop sessions.
Look for Regional or Browser Issues
Sometimes the code itself is fine, but the login page creates the appearance of failure.
Browser extensions, blocked scripts, VPNs, and strict privacy settings can interfere with sign-in flows on sites like Google, Microsoft, GitHub, and Amazon.
- Try a private window or another browser.
- Disable ad blockers and script-blocking extensions temporarily.
- Turn off VPN or proxy services and retry.
- Clear cookies for the affected site if the login loop persists.
If the code works in one browser but not another, the issue is likely with the login session rather than 1Password.
Use Backup Codes if You Are Locked Out
If you cannot get the authenticator code accepted after multiple attempts, use backup codes if the service provides them.
Many platforms offer one-time recovery codes during two-factor setup, and those are the fastest way to regain access.
Store backup codes somewhere separate from your primary vault if your security policy allows it.
If you have already exhausted them, contact the service’s account recovery or support flow and verify identity through the official process.
How to Prevent 1Password Authenticator Problems Later
Once you regain access, a few habits can reduce future failures.
The key is to keep the secret, time, and account state aligned across all devices.
- Keep automatic time enabled on every device.
- Review authenticator items after device migrations.
- Use one login item per account to avoid duplicates.
- Store backup codes in a secure, separate recovery location.
- Test new authenticator setups before assuming they are complete.
For teams, document which identity provider or app owns each two-factor method, especially when accounts are tied to Microsoft Entra ID, Google Workspace, Okta, or Duo Security.
When to Contact 1Password Support or the Service Provider
If you have checked time settings, sync status, account selection, and setup secrets but the code still fails, the problem may require support intervention.
1Password support can help you verify app behavior, but only the service provider can reset a broken 2FA enrollment on their side.
Be ready to share the device type, app version, affected account, and exact error message.
If this is a work account managed by an administrator, your IT team may need to re-enroll your authenticator method or restore access through a policy-driven recovery process.