If you need a reliable way to regain access to Authy, the problem is often tied to device sync, network settings, or an outdated app.
This guide explains how to fix Authy not working with practical steps that cover common mobile and desktop failures.
Why Authy stops working
Authy is a two-factor authentication app from Twilio that protects accounts with time-based one-time passwords, backup codes, and multi-device support.
When it fails, the cause is usually not the codes themselves but a problem with phone number verification, device registration, push notifications, account migration, or a broken app session.
Because Authy depends on both local device data and cloud-synced account information, even a small issue can block sign-in.
That is why the fix often starts with simple checks before moving to more advanced recovery steps.
Check whether the problem is with Authy or a specific account
Before changing settings, confirm whether Authy is broken for one service or across all accounts.
If only one site rejects your code, the issue may be with that site’s clock drift, a stale token, or a recently reset 2FA enrollment.
If every code fails, the issue is more likely Authy itself.
- Test Authy on more than one service, if available.
- Confirm the code changes every 30 seconds.
- Check whether the app opens normally and shows your tokens.
- Look for error messages about verification, sync, or registration.
Verify your device clock and time zone
Time-based one-time passwords depend on accurate device time.
If your phone or computer clock is off by even a few seconds, Authy codes may be rejected by the service you are trying to access.
What to do
- Turn on automatic date and time settings on your phone.
- Set the correct time zone, especially after travel.
- Restart the device after adjusting time settings.
- Check the same setting on a desktop app if you use Authy there.
This is one of the fastest fixes when authentication fails even though the app appears normal.
Update Authy to the latest version
An outdated version of Authy can create sync problems, crash during startup, or fail to validate tokens properly.
App updates often include security patches and compatibility fixes for iOS, Android, Windows, and macOS.
Open the App Store, Google Play Store, or the desktop app updater and install the latest release.
If updates are already enabled, force a manual update to ensure you are not running an older build with a known bug.
Restart the app and the device
Temporary memory issues can stop Authy from loading tokens or refreshing its session.
A full restart clears background processes and reconnects the app to network and system services.
- Close Authy completely, not just minimize it.
- Restart your phone, tablet, or computer.
- Reopen the app and wait for it to finish syncing.
- Try generating a new code after the restart.
If the app works after rebooting, the issue was likely a temporary process conflict rather than account corruption.
Check your internet connection and network restrictions
Authy needs network access for initial setup, device verification, and account synchronization.
Weak Wi-Fi, captive portals, VPNs, firewalls, or corporate proxy rules can interrupt those requests.
What to check
- Switch between Wi-Fi and mobile data.
- Disable VPN software temporarily.
- Test another network if you are on public Wi-Fi.
- Make sure your firewall does not block Authy on desktop.
- Confirm your browser or system can reach normal HTTPS sites.
If Authy opens but cannot verify your account or sync codes, a network restriction is a likely cause.
Confirm your phone number and account registration
Authy is tied to a phone number, and problems often start when a user changes numbers, reinstalls the app, or tries to register on a new device.
If the number on file is no longer active, you may not receive the verification prompt needed to restore access.
Make sure the phone number in Authy matches the number you originally registered.
If you changed numbers, review whether you enabled phone number migration or updated your account in advance.
If you still have access on another trusted device, use it to confirm the account status before making changes.
Review multi-device and backup settings
Authy supports multi-device access, but that feature can create confusion if a new install is blocked or if a device was removed from your trusted list.
Some users also disable multi-device support for security, then forget that a new device will need reauthorization.
Check whether your account allows multi-device access and whether the device you are using was previously approved.
If you rely on backups, confirm that encrypted backups are enabled and that you can still restore the account using the same phone number and trusted device flow.
Fix Authy desktop app issues
The desktop version can fail for reasons that do not affect the mobile app, including damaged cache files, permission issues, or OS-level security settings.
This is common on Windows and macOS after updates or permission changes.
Desktop troubleshooting steps
- Quit Authy completely and relaunch it.
- Run the app with normal user permissions.
- Check whether antivirus or endpoint protection is blocking it.
- Install the latest OS updates.
- Remove and reinstall the app only if you still have account access on another trusted device.
If the desktop app shows blank screens or never finishes loading, reinstalling may help, but only after confirming your account can be recovered safely.
Clear app cache or reinstall safely
Corrupted local app data can prevent Authy from opening correctly or displaying your codes.
On mobile, clearing cache may solve the issue without removing your account.
On desktop, reinstalling can reset broken application files.
Before reinstalling, make sure you have a trusted recovery path.
If you only have one device and no backup access, uninstalling could make recovery harder.
Whenever possible, verify that you can still sign in through another device or that your backup setup is intact.
Regain access if Authy is locked or you lost a device
If you cannot open Authy at all, start with the account recovery options available through Twilio Authy support.
In many cases, recovery depends on your registered phone number and proof that you still control the account.
Common recovery paths include:
- Using an existing trusted device that still shows your tokens.
- Requesting access through your registered phone number.
- Following account recovery or device reset instructions from Authy support.
- Re-enrolling two-factor authentication on important accounts once access is restored.
Be careful not to reset a service’s 2FA before confirming another working sign-in method, such as backup codes, a security key, or a secondary recovery email.
When the problem is with the website or service
Sometimes Authy is functioning correctly, but the destination service is not accepting the code.
This can happen after a 2FA reset, a server-side outage, a clock sync problem, or an expired token enrollment.
If you suspect the website is the issue, check its status page, retry the login in a fresh browser session, and confirm that you are using the right Authy entry for that account.
For critical services, keep backup codes and a hardware security key ready as a fallback.
How to prevent Authy issues in the future
Once Authy is working again, a few habits can reduce the chance of another lockout.
These steps improve recovery options and make two-factor authentication easier to manage over time.
- Keep at least one trusted backup method for important accounts.
- Enable automatic time and date on all devices.
- Update Authy and your operating system regularly.
- Save recovery codes in a secure password manager.
- Review your trusted devices after changing phones or numbers.
- Avoid uninstalling Authy unless you know how to recover the account.
For users managing business or high-value accounts, a hardware security key and a documented recovery process can prevent downtime if Authy becomes unavailable again.