TRY NOW
book meeting
BACK TO KB LIST

Standalone Veeam Agent for Unix Fails to Connect to Veeam Backup Server After Certificate Changed Twice

KB ID: 4895
Product: Veeam Backup & Replication | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1
Veeam Agent for IBM AIX | 4.0 | 4.1 | 4.5 | 4.6 | 4.6.1 | 13 | 13.1
Veeam Agent for Oracle Solaris | 4.0 | 4.1 | 4.5 | 4.6 | 4.6.1 | 13 | 13.1
Published: 2026-08-05
Last Modified: 2026-08-05
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

Veeam Agent for IBM AIX or Veeam Agent for Oracle Solaris operating in standalone mode is unable to connect to its configured Veeam Backup Server. Backup jobs fail to start, and attempts to resynchronize or edit the connection fail with the following error:

Self-signed certificate

This behavior occurs after the SSL certificate on the Veeam Backup Server has been changed twice since the agent last connected successfully.

Cause

This issue occurs because Veeam Agent identifies the Veeam Backup Server by the certificate stored in the agent's local database, and the Veeam Backup Server retains only its current certificate and the one immediately preceding it. When the certificate is changed while the agent is connecting regularly, the agent finds its stored certificate among those retained, confirms that the server is unchanged, and records the new certificate. When the certificate is changed a second time before the agent has reconnected, the certificate stored by the agent is no longer retained by the Veeam Backup Server. The agent cannot confirm that the server is the same one it was configured for, and the connection is refused.

Solution

New Backup Chain After Reconnecting

Deleting and recreating the connection to the Veeam Backup Server causes each recreated job to start a new backup chain. The first run of each recreated job will be a full backup.

To restore connectivity, the existing connection to the Veeam Backup Server must be recreated so that the current certificate is accepted. Before that can be done, the jobs that use the connection must be deleted, allowing the backup server to be removed and re-added. The backup jobs can then be recreated. Backup files created by those jobs are not deleted and remain in the repository.

Part 1: Job Removal

  1. Review the configured jobs [AIX|Solaris] and identify those that use the affected Veeam Backup Server:
veeamconfig job list
  1. For each identified job, review and take note of its settings [AIX|Solaris] to help with job recreation later.
veeamconfig job info --name <job_name>
  1. Delete each job that uses the affected Veeam Backup Server [AIX|Solaris]. The --force option is required because the certificate error also prevents the standard deletion from completing:
veeamconfig job delete --name <job_name> --force

Part 2: Remove and Re-add Veeam Backup Server

  1. Review the configured Veeam Backup Server connections [AIX|Solaris] to identify the affected connection:
veeamconfig vbrserver list
  1. Delete the affected connection [AIX|Solaris]:
veeamconfig vbrserver delete --name <vbr_name>
  1. Create the connection again [AIX|Solaris], and accept the new certificate when prompted:
veeamconfig vbrserver add --name <vbr_name> --address <vbr_address> --login <username>

Part 3: Recreate the Jobs

  1. Recreate the jobs that were deleted in Step 3 [AIX|Solaris].

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.