#1 Global Leader in Data Resilience

Hotfix to Improve Handling of Self-Signed Certificates Used By On-Prem Object Storage with IAM/STS Endpoints, Agent, VM jobs, and Cloud Connect

KB ID: 4498
Product: Veeam Backup & Replication | 12
Veeam Cloud Connect | 12
Published: 2023-10-05
Last Modified: 2023-10-19
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.

Article Applicability

The hotfix discussed in this article is only necessary when using an on-prem object storage appliance that utilizes self-signed certificates, and you are being affected in the ways described in the Resolved Issues section.

If you are not experiencing the errors listed in this article or are not using the features mentioned, there is no need to request this hotfix.

Note: Hotfixes are created and distributed to expedite the resolution of an acute issue that a future release release of the software will resolve. As such, hotfixes are only distributed to customers experiencing the issue that the hotfix will resolve.

Requirements

Before requesting and applying this hotfix, ensure that Veeam Backup & Replication 12 P20230718 is installed. You can check the installed build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Resolved Issues

This hotfix improves how Veeam Backup & Replication 12 manages self-signed certificates used by on-premises object storage when the self-signed certificates have not been manually imported, resolving the following issues:

  • Saving IAM/STS endpoints for a repository fails with the following errors:
    Failed to find valid gateway server for non-scheduled repository <repo_name>: Unable to verify certificate: certificate host name validation failed
    
    Unable to change encryption settings because the object storage repository is unavailable. Ensure the repository is reachable from the backup server and try again.
    
  • Agent jobs targeting repositories with IAM/STS, including Cloud Connect, fail when tenants have not manually imported the self-signed certificates, leading to the error:
    A WebException with status TrustFailure was thrown
    
  • Running VM jobs (IAM/STS and Insecure Direct) in Cloud Connect cases fails with:
    Amazon S3 Compatible connection has returned an untrusted certificate.
    

Both the Service Provider and their Tenants must install this hotfix to resolve these issues.

Download Information

To acquire this hotfix, please create a case with Veeam Support requesting the hotfix associated with Issue ID#577015.


To prevent conflicts with existing hotfixes that may be installed, a support case must be created to acquire this hotfix so that Veeam Support can assess whether the patched files of this hotfix conflict with any hotfix that may already be installed.

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

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.