Discussions related to using object storage as a backup target.
Locked
dali@iae.nl
Enthusiast
Posts: 82
Liked: 21 times
Joined: Jan 17, 2022 10:31 am
Full Name: Da Li
Contact:

[SOLVED] VBR 11a can not browse AWS S3 Buckets

Post by dali@iae.nl »

On Windows Server 2019 no problems, but on Windows Server 2022 cannot connect to AWS S3.
Tested on different servers. Now used new created clean 2022 Server + Veeam 11a latest patch P20211211. Firewalls on or off no change.
In the "New Object Storage Repository", "Bucket", when click on the Browse Button is gives: "Failed to list S3 buckets: check if the specified account has required permissions.".
On the same 2022 server, using the S3 Browser and the same credentials there is no problem. Is this a bug?
Andreas Neufert
VP, Product Management
Posts: 7081
Liked: 1511 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: VBR 11a can not browse AWS S3 Buckets

Post by Andreas Neufert »

Does the server has general access to the internet and DNS is working correctly so that it can check the certificates used for the https connection ?
dali@iae.nl
Enthusiast
Posts: 82
Liked: 21 times
Joined: Jan 17, 2022 10:31 am
Full Name: Da Li
Contact:

Re: VBR 11a can not browse AWS S3 Buckets

Post by dali@iae.nl »

Yes, the 3 certificates can be downloaded without problems (stated in https://www.veeam.com/kb3215). And I did a fresh install of windows 2022 with DNS 1.1.1.1 and downloaded from this server the Veeam ISO and patch.
And also with the renkey S3TLSRevocationCheck = 0 did not help.
dali@iae.nl
Enthusiast
Posts: 82
Liked: 21 times
Joined: Jan 17, 2022 10:31 am
Full Name: Da Li
Contact:

Re: VBR 11a can not browse AWS S3 Buckets

Post by dali@iae.nl » 1 person likes this post

Sorry, I can download the certificates on other servers but not on the Win 2022 servers.
Although I cannot download the certificates securely, it seems to be a timing issue as found in the C:\ProgramData\Veeam\Backup\Satellites\VBR\VBR_Administrator\Agent.PublicCloud.Satellite.log file --> "3 error: The difference between the request time and the current time is too large."
Corrected the exact time and now I can list the S3 buckets. Case closed.
Locked

Who is online

Users browsing this forum: No registered users and 4 guests