Fatal Error running S3 (Wasabi) job using 2.1.0.5_stable_2025-03-04 on Debian after upgrade

Support
1

Hi all brave ones.

After a lifetime of successful backup jobs, I’ve seen things go south after I upgraded to version 2.1.0.5_stable_2025-03-04. (see the attached image)

I appreciate any help you could provide, as I’m hesitating to use AI to resolve this.

Thanks

-RA

Captura de tela de 2025-04-15 10-18-45
Captura de tela de 2025-04-15 10-18-45881×1014 119 KB

2

Issue has been resolved.

3

Hi @Rodolpho_Arruda, glad to hear about a lifetime of successful backups. Do you mind sharing what was the solution to your issue?

4

It would be great to hear from @Rodolpho_Arruda about the real cause, but the error message usually means one of these two:

  • Incorrect password to the service
  • Clock is not in sync

Both cases will cause the S3 signature to be deemed incorrect and gives the error message shown.

It can of course happen with other similar things, like signing method version, etc.