Operational Defect Database
BugZero found this defect 228 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4498
Hotfix to Improve Handling of Self-Signed Certificates Used By On-Prem Object Storage with IAM/STS Endpoints, Agent, VM jobs, and Cloud Connect
Last update date:
10/19/2023
Affected products:
Veeam Backup & Replication
Veeam Cloud Connect
Affected releases:
12
Fixed releases:
No fixed releases provided.
Description:
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.
