File System Remote (S3-Wasabi) Access Keys expired or mangled?

[klou]

Context

• XO origin: the sources
• Versions:
  • xo-web: 5.68.0
  • xo-server: 5.65.0

Expected behavior

Create Access Key in Wasabi. Input Access Key in XO. Key and access to S3 bucket persists throughout several weeks, until Key is de-activated.

Current behavior

I created a new key on 8/26, and put the credentials in XO. Subsequent backups and access tests worked, with the last known good backup occurring 8/31.

9/4 backups fail, with The request signature we calculated does not match the signature you provided. Check your key and signing method. The Access Keys in wasabi are still active, and I can't find anything relating to an auto-expiration.

File System Remote write tests (from the GUI) fail on 9/8, with the above error.

This looks to be the 3rd time (or so) that this has happened, but I haven't kept track to to see if there's a definite timeline.

[nraynaud]

Hi, thanks for the report.

I reproduce the bug from times to times, but I have not yet pinpointed its origin.

The work around I found is a bit convoluted:

• restart XO (the error "sticks" until the node process is restarted)
• test the S3 remote in settings->remotes->test your remote (the medical bag icon)
• then the backup should be ok for the duration of the XO process

[klou]

Can confirm, works after restarting the host VM (was easier at the moment than just restarting XO).

Also, FWIW worked on 9/10, failed on 9/11. So no obvious correlation with timelines.