How to Fix Authenticator Codes: Difference between revisions
Jump to navigation
Jump to search
Cmseditors (talk | contribs) No edit summary |
Cmseditors (talk | contribs) No edit summary |
||
| (19 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
My authenticator app generates codes that don't work. | My authenticator app generates codes that don't work. | ||
==Causes== | |||
One of the main reasons and the most common one for “Incorrect Code” error that the time on your 2-Factor Authenticator app is not synced correctly. If you want to make sure your time is set correctly please follow the instructions below. | |||
==Solutions== | ==Solutions== | ||
*Each code is only valid for a short period of time. Try using a new code. | *Each code is only valid for a short period of time. Try using a new code. | ||
*Make sure the time on your phone matches the time on your computer. | *Make sure the time on your phone matches the time on your computer. | ||
: | :-Go to your device's settings. | ||
:-Find and select "Date & Time". | |||
: | :-Ensure "Use network-provided time" or "Automatic date & time" is enabled. | ||
: | :-If already enabled, try toggling it off and then back on. | ||
: | |||
*The "Time correction for codes" option was removed in the latest Google Authenticator updates because modern versions are designed to automatically sync the time with Google's servers, making manual corrections unnecessary. If your codes aren’t working correctly, it could be due to a mismatch between your device’s time settings and Google’s servers. To fix this, ensure your device’s time and date settings are set to "Automatic" or synced with the network. On most devices, you can adjust this in the general settings under "Date & Time." This should resolve any timing issues with the codes. | |||
*If the problem persists, try removing and re-adding the account to Google Authenticator by typing the key provided by the Call Manager support team. This refreshes the connection and ensures the codes are accurate [[Multi-Factor_Authentication_(MFA)]]. | |||
* | *Also, check if the time on your computer is set correctly. The authenticator is time-stamped, so if the two do not match it will not work. | ||
*Connect to the call manager from Chrome. | |||
[[Category:FAQ]] | [[Category:FAQ]] | ||
Latest revision as of 18:22, 30 July 2025
My authenticator app generates codes that don't work.
Causes
One of the main reasons and the most common one for “Incorrect Code” error that the time on your 2-Factor Authenticator app is not synced correctly. If you want to make sure your time is set correctly please follow the instructions below.
Solutions
- Each code is only valid for a short period of time. Try using a new code.
- Make sure the time on your phone matches the time on your computer.
- -Go to your device's settings.
- -Find and select "Date & Time".
- -Ensure "Use network-provided time" or "Automatic date & time" is enabled.
- -If already enabled, try toggling it off and then back on.
- The "Time correction for codes" option was removed in the latest Google Authenticator updates because modern versions are designed to automatically sync the time with Google's servers, making manual corrections unnecessary. If your codes aren’t working correctly, it could be due to a mismatch between your device’s time settings and Google’s servers. To fix this, ensure your device’s time and date settings are set to "Automatic" or synced with the network. On most devices, you can adjust this in the general settings under "Date & Time." This should resolve any timing issues with the codes.
- If the problem persists, try removing and re-adding the account to Google Authenticator by typing the key provided by the Call Manager support team. This refreshes the connection and ensures the codes are accurate Multi-Factor_Authentication_(MFA).
- Also, check if the time on your computer is set correctly. The authenticator is time-stamped, so if the two do not match it will not work.
- Connect to the call manager from Chrome.