TRY NOW
book meeting
BACK TO KB LIST

Impact of Domain name or Hostname Change on Veeam Appliances

KB ID: 4781
Product: Veeam Backup & Replication | 13
Published: 2025-11-13
Last Modified: 2026-11-09
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

After changing the FQDN of a Veeam Appliance—either by adding it to a domain or changing its hostname—some operations may be impacted.

Solution

Services Restart When the Hostname Changes

After the hostname of the Veeam Software Appliance is changed, all services running on the appliance are restarted. Backup and restore operations performed by jobs running at that time will fail. For more information, see Veeam Backup & Replication User Guide: Changing Server Name.

SAML Authentication May Stop Working

After the host name of the Veeam Software Appliance is changed, the Service Provider (SP) information will change.

There will be a new SP Entity ID and Assertion Consumer Service URL. These should be updated on the Identity Provider side, either manually or by using the Download option within the Veeam Backup & Replication console to then upload the new SP metadata.

The "Identity Provider" tab of the "Users & Roles" settings window is shown, with SAML authentication enabled. The screen displays identity provider (IdP) information such as Entity ID, Redirect URL, and Logout URL. Below, a highlighted section labeled "Service Provider (SP) information" provides certificate details, download links for metadata, and manual configuration values including SP Entity ID / Issuer and Assertion consumer URLs. The OK and Cancel buttons are visible at the bottom.

Host Connectivity to Deployer Breaks

After changing the hostname or FQDN of a Veeam Infrastructure Appliance or Veeam Hardened Repository, the deployer certificate will be regenerated. To reinitialize the connection between Veeam Backup & Replication and the appliance, you must re-run the JeOS host wizard to restore connectivity with the deployer.

  1. Update the Managed Server's entry within the Veeam Backup & Replication Console using KB1905.
  2. With the entry within the Veeam Backup & Replication Console now updated so that the software will attempt to reach the Veeam Appliance using the correct hostname or FQDN, you must reinitialize the connection to the managed server.
    1. Reset the pairing code on the Infrastructure Appliance.
    2. Open the Veeam Backup & Replication Console and edit the Managed Server for the JeOS host whose hostname or FQDN was changed.
    3. Click Next through each step, and when prompted to "Connect using a pair code?" select Yes, and provide the Pairing Code.
      Note: The pairing code remains valid for 30 minutes.

      Veeam Backup & Replication Web UI Example:
A Veeam Backup and Replication dialog box displays an error message: "Failed to connect to deployer service, host '172.25.99.34,...', port '6160'. Failed to check deployer service compatibility. Authentication failed, see inner exception. An unknown error occurred while processing the certificate." The dialog asks, "Connect using a pairing code?" with "Yes" and "No" buttons for user selection. The background shows the "Edit Linux Server" configuration screen.
A "Pairing Code" dialog box is open on top of the Veeam "Edit Linux Server" setup screen. The dialog instructs the user to enter a code to pair a Linux host provisioned from Veeam JeOS ISO with the backup server. The pairing code field contains "95767," and there are "OK" and "Cancel" buttons below for user confirmation. The main wizard background shows configuration options for the Linux server.
Veeam Backup & Replication Console (Windows-based):
A Veeam Backup and Replication dialog box displays an error message: "Failed to connect to deployer service, host '172.25.99.34,...', port '6160'. Failed to check deployer service compatibility. Authentication failed, see inner exception. An unknown error occurred while processing the certificate." The dialog asks, "Connect using a pairing code?" with "Yes" and "No" buttons for user selection. The background shows the "Edit Linux Server" configuration screen.
A "Pairing Code" dialog box is open on top of the Veeam "Edit Linux Server" setup screen. The dialog instructs the user to enter a code to pair a Linux host provisioned from Veeam JeOS ISO with the backup server. The pairing code field contains "95767," and there are "OK" and "Cancel" buttons below for user confirmation. The main wizard background shows configuration options for the Linux server.

Manually Configured Veeam Plug-ins Fail to Connect

After the hostname of the Veeam Software Appliance is changed, the TLS certificate of the Veeam Backup Server is regenerated. Veeam Plug-ins that were installed and configured manually retain the fingerprint of the previous certificate, and backups fail with the following error:

Failed to establish ssl connection

This error occurs even if the plug-in is configured to connect to the Veeam Backup Server by IP address.

To restore connectivity, perform the following steps on each affected server. The example commands are for Veeam Plug-in for Oracle RMAN on Linux or Unix.

If the plug-in connects to the Veeam Backup Server by hostname, specify the new hostname first:

OracleRMANConfigTool --set-host <new_hostname>

Specify the credentials again and confirm the new Veeam Backup Server fingerprint when prompted:

OracleRMANConfigTool --set-credentials 'DOMAIN\username' 'password'

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.