The object storage server security certificate is not valid. Examine and accept the certificate.

[fborup]

The error: The object storage server security certificate is not valid. Examine and accept the certificate.

The whole story:

I´ve installed V5 on late March and everything was running fine until April, 12th
Suddenly I got the error:


14/04/2022 11:14:14 71 (2396) Delaying next try to 14/04/2022 11:44:14 (UTC: 14/04/2022 14:44:14)...
14/04/2022 11:27:11 11 (2112) Getting object Veeam/Backup365/BackupRepository/RepositoryLock/ce7d10a1a43a46b4a154bebe8ff92147_8d16143b6b9b4fb09dbad43892da2465 from bucket backupo365s3bucket...
14/04/2022 11:27:11 11 (2112) Object storage repository lock update failed (repository ID: 8d16143b-6b9b-4fb0-9dba-d43892da2465)
14/04/2022 11:27:11 11 (2112) Error: The object storage server security certificate is not valid. Examine and accept the certificate.
14/04/2022 11:27:11 11 (2112) Type: Veeam.Archiver.Repository.ObjectStorage.Common.ObjectStorageOperationFailed
14/04/2022 11:27:11 11 (2112) Stack:
14/04/2022 11:27:11 11 (2112) at Veeam.Engine.Request.RequestRetry.Execute[T](Func`1 exec, Action onFailedTry)
14/04/2022 11:44:14 22 (1092) Activating job: Backup SharePoint Online - Backup Repo Plus AWS S3 Bucket...

AWS checked, IAM, Bucket persmissins, everthing is fine and the ID can uplaod and download objects to/from the bucket with no problem

There is a Debug file?


I treid to restart services, reboot, update Patches, nothing, same error

[jorgedlcruz]

Good morning,
I see some other users with similar errors that were related to the Internet Proxy configuration, any change on that regards at all?

Also, I would recommend you upgrade to the latest version, v6 with latest hotfix, or to the minimum, perhaps double check you have latest v5 cumulative update:
https://www.veeam.com/kb4106

If none of that helps, last step would be to open a support ticket, so our Support Engineers can help you much better looking at the logs, etc.

Give that a try, and let us know.

We are here to help.

[fborup]

An intersting test: Using a network traffic monitor, there is no network traffic being detected during the error, the error tooks a split second to show up and there is no outbound network traffic

[fborup]

An intersting test: Using a network traffic monitor, there is no network traffic being detected during the error, the error tooks a split second to show up and there is no outbound network traffic

I´m running : 5.0.3.1033

I´ll try to upgrade
I have the community edition, so, it will take some time to someone pick my ticket up

[fborup]

No luck!
15/04/2022 23:23:29 :: The object storage server security certificate is not valid. Examine and accept the certificate.
Running:
Veeam Backup for Microsoft Office 365 5d Cumulative Patch KB4278 5.0.3.1063 10.0.5.1063 2022-02-08

[jorgedlcruz]

I can see you are working with support, and all the updates are there, so let's wait for support to pick it up.

What happens if you go the Object Storage Repository, and the edit, and follow all the steps, at that point it checks connectivity, including SSL.

If it was working before but suddenly stopped. Any Networking change, that happened? Any Firewall introduced? Does your server need an Internet Proxy to navigate the Internet?

Let us know

[Mike Resseler]

@fborup

Unless I need more coffee in the morning, but I can't see the support ticket number. Can you post it here? Thanks

[fborup]

I´m still figuring out exaclty why, but the short: My UTM Firewall was making the connection to consider the Starlink Root crtificate to be invalid.
The short-term solution it was to force deep inspection/SSl inspection + WebFilter and worked well.

Well, why does the FW was tampering in such way, on even with no filter, to not trust the root, it´s a mistery curently still under investigation
"[The issuer of this certificate could not be found.", when subject to sslinepction to filter put traffic, the problem went away

[jorgedlcruz]

Thank you for coming back to us. It was clear it was on that direction, something tampering with the VB365 server connection to an HTTPS destination, S3 in this case

I saw this in the past on Fortigate, and saw it as well with the old but gold, Microsoft ISA (Forefront). Years and years ago, but same issue.

Thanks for sharing so in the future others can find it on google.