Is anyone familiar with such an error, in block below? It looks misleading as I don't see how would a user for the access key disappear or lose it as a property. We use 1 user and 1 access key in the environment and other backup jobs are all good.
4/24/2023 6:13:22 PM :: Processing b4dae1e7-22d5-4d61-a43f-44156dd50331 Error: REST API error: 'S3 error: Cannot find user for the access key.
Code: NoSuchEntity', error code: 404
Other: HostId: 'tt+qtWw///r4xForpKKJylsyepKlQ5IoGa3GLNqbNPtRFCZfK1w26RgzgSRvNb5JXVgl9WTdXRB+'
write: An existing connection was forcibly closed by the remote host
I'm seeing such errors and HTTP 403 occasionally for some tasks. As it resolves itself with the next offload, my suggestion was that such errors are generated on the Wasabi side when too many requests occur.
Are you already on V12 with the latest Patch? Maybe this could resolve such issues:
Capacity Tier offload fails with the following errors due to a lack of full S3 protocol compatibility on some S3-compatible object storage systems:
Impossible to start a new log because there are other logs
or
Invalid log sequence
or
S3 error: Access Denied