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 |
Oops! Something went wrong.
Please, try again later.
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
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.
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.
