Location of S3 backup settings

Maintenance
1

hello. I am try to S3 backups working to a non-aws S3 storage system, on two miab instances, at two locations. I have it working on one, but not the other. So, I am am trying see where the configuration settings, .conf or whatever, in the file system are located. Can anyone help? Thanks :slight_smile:

2

You should be able to do it all from the admin panel. On the filesystem, I think all backup settings are stored in /home/user-data/backup/custom.yaml

1 Like
3

Hi. Thanks for that, much appreciated & was what I was looking for. The error messages in the Backup admin panel are not specific enough to troubleshoot issues. e.g., one just says “Enter an S3 bucket name.” even if there is one named. I was able to copy the config to the other machine, modify slightly & test. It didn’t work, but at least I know it was not the configuration that’s the problem. Iz

4

Just to help as I got it working but the panel looks quite different then several version ago when I entered it. The yaml should look like:

target: s3://region.amazonaws.com/bucketname/
target_pass: secret key
target_user: access key

At least that is how my working config looks :wink:

replace region, bucketname and the rest with your settings.

5

Hi there. Thank you for your comment, that is how the yaml file was structured. Of the two systems I am working with, one is on a VPS, and is working ok, albeit with the duplicity error below. It only differs from the recommended install in that it is running on ARM, not x86. It’s been going fine. The other is self hosted at home, on x86 bare metal. The email side works fine, email flows & certs install. But the non-AWS S3 is causing problems. I can connect to my bucket with RClone, https etc but not MIAB. It could be any number of issues. I’m still experimenting - might get there eventually!
Errors, for example:

WARNING 1
. WARNING: Using boto3 >= 1,36.0 with non-amazon s3 services may result in checksum errors. a workaround is to set the following env vars
*. *
. export AWS_REQUEST_CHECKSUM_CALCULATION=when_required
. export AWS_RESPONSE_CHECKSUM_VALIDATION=when_required
*. *
. see boto3 1.36+ breaks Duplicity...but there is a workaround (#870) ¡ Issues ¡ duplicity / duplicity ¡ GitLab for details.

Attempt of list Nr. 1 failed. SSLError: SSL validation failed for https://object-storage.nz-por-1.catalystcloud.io/mailtwo hostname ‘object-storage.nz-por-1.catalystcloud.io’ doesn’t match either of ‘autoconfig.mail.abcd.xyz’, ‘autodiscover.mail.abcd.xyz’, ‘mail.abcd.xyz’, ‘mta-sts.mail.abcd.xyz’
WARNING 1

Thanks, Iz