TRY NOW
book meeting
BACK TO KB LIST

The provided one-time code is incorrect. Check if the backup server time is correct.

KB ID: 4739
Product: Veeam Backup & Replication | 13
Published: 2025-09-03
Last Modified: 2026-06-03
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

When attempting to connect to the Veeam Host Management Console, after entering the MFA TOTP code, the following error occurs:

The provided one-time code is incorrect. Check if the backup server time is correct.
Screenshot showing a failed attempt to sign in using an MFA TOTP code. The error discussed is highlighted.

Solution

There are two potential causes for time mismatch:

Cause 1: Hypervisor Time Synchronization Is Overriding Guest Time

When the Veeam Backup & Replication Veeam Software Appliance is deployed on a VM within a Virtual Environment, if the VM is configured to synchronize its time with the hypervisor, the hypervisor may override the system time the guest OS pulls from the NTP server.

It is recommended to disable time synchronization between the hypervisor and the Veeam Software Appliance VM.

This may look different in different hypervisors. For example, in VMware, this option is available in the VM Options:

Screenshot of VM's VM Options table with the VMware Tools section expanded and the option for Synchronize at started and resume disabled.
This is an example of the Time syncronization option in Hyper-V:
Screenshot of a Hyper-V VM's settings with the Integration Services section selected and the option for "Time syncronization" disabled.

Cause 2: The NTP Server Cannot be Contacted or Provides an Invalid Time

 

Update NTP via Veeam Host Management Console WebUI

If access to the Veeam Host Management Console is possible (e.g., the issue is intermittent or another Host Admin has MFA disabled for their account), the NTP servers can be configured using the web UI.

Screenshot of the Veeam Host Management Console with the Time section selected and the options for Add, Edit, and Remove are highlighted to indicate how NTP servers can be modified
Update NTP via Veeam Live OS ISO

If there is no access to the Veeam Host Management Console, then the configuration of the Veeam Software Appliance must be modified using the Veeam Live OS ISO.

  1. Mount the Veeam Live OS ISO.
  2. Restart the host.
  3. Boot from the Veeam Live OS ISO.
Screenshot of Veeam Live grub boot menu showing "Start Veeam Live" highlighted.
  1. Log in with the root / veeam credentials.
  2. Run the following command to mount the VSA system:
veeam_mount_system
  1. Run the following command to enter the chroot of the main system:
veeam_chroot_system
screenshot of terminal showing the previous commands being executed
  1. Using vi, edit the /etc/chrony.conf file and specify the correct NTP server for synchronization.
vi /etc/chrony.conf
screenshot of a modified version of the /etc/chronyd.conf file with the NTP server set as pdcntp01.domain.tld
Example /etc/chronyd.conf
  1. Manually set the system time so that it is close enough for chronyd to maintain.
    The configured time-synchronization policy prevents chronyd from stepping the clock in large jumps, so the time must be corrected manually first.
Set the Time in the Appliance's Configured Timezone

Running the date command displays the active timezone abbreviation (for example, CEST). Enter the new time in that same timezone. There is no need to adjust for daylight saving time.

# Display the current system time and timezone
date
# Set the system clock using the timezone shown above (24-hour format)
date -s "YYYY-MM-DD HH:MM:SS"
# Write the corrected time to the hardware clock
hwclock --systohc
  1. Run the command exit to exit the chroot, and then reboot the system.
screenshot showing the commands to exit the chroot and reboot the machine.
After booting the system with the correct NTP server, the time should be synchronized, and MFA will work correctly.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.