Joplin fails to sync with Wasabi (which is AWS compatible)

Operating system

Linux

Joplin version

3.2.8

Desktop version info

Joplin 3.2.8 (prod, linux)

Client ID: f655d64d714a49c1a59208aa8da60a1c
Sync Version: 3
Profile Version: 47
Keychain Supported: No

Revision: d458648

Backup: 1.4.2
Conflict Resolution: 1.2.3
Freehand Drawing: 2.13.0

Sync target

S3

What issue do you have?

I am migrating from a discontinued note application to joplin.

I am trying to set up sync from Joplin to Wasabi. Wasabi claims to be AWS compatible.

I have set up my Wasabi bucket.

In joplin I have set the bucket name. I have set the S3 URL, S3 region, S3 access key, and S3 secret key. These credentials are the same as I use with my borg backup bucket, which is working perfectly.

Joplin provides a "check synchronization configuration" facility. It reports "Success! Synchronization configuration appears to be correct."

When I tell joplin to sync I get the following response:

"Last error: SignatureDoesNotMatch: Could not upgrade from version 0 to version 1: The request signature we calculated does not match the signature you provided. Check your key and signing method."

I can not find anything about "signing method" in my joplin configurarion interface.

Since I am using a set of credentials that are working for another bucket I do not know how to proceed.

Screenshots

This might help.