I found the issue!
Scaleway provides a URL for the endpoint of
https://bucketname.s3.fr-par.sc.cloud, complete with a “Copy” button, which will vary according to your data centre and bucket name. So that’s what I used.
When I used the inspector to look at the requests to MIAB, I was interested in the end of the URL, but I then noticed that the URL started with
s3://https://, which looks very wrong. So I wondered if MIAB was not expecting a URL like that but just a hostname. So I tried it without the prefix… which didn’t work either, but it showed me a different error complaining about host names. I noticed that the s3cmd config wanted a host name both with and without the bucket name, so I tried without, and that worked!
So, if your Scaleway endpoint is provided as
https://bucketname.s3.fr-par.scw.cloud, and you’re backing up to a folder called
mail within that bucket, your MIAB settings should be:
- S3 Region:
- S3 Host / Endpoint:
s3.fr-par.scw.cloud (notice it does not include the bucket name)
- S3 Path:
After all that, MIAB replied with “OK”, so I’ll wait to see if the backup goes ahead later tonight.
I also checked some of the earlier things we were suspicious about, and it works fine if your bucket name includes dashes.
This could have been avoided with some better labelling on the fields, perhaps some tooltips?