Backup to S3 fails after update to v71a

Help with Setup/Upgrade
1

Hello community,

i have currently the issue, that the backup to s3 fails with a signature mismatch.
The error itself is thrown from the S3 provider (Scaleway).

Steps, that is tried to mitigate this issue:

  • Re-added the credentials for S3 along with a different bucket → Same result
  • Updated duplicity to latest version from duplicity ppa (duplicity 3.0.3.2 November 25, 2024)
  • Ran the backup directly via mailinabox/management/backup.py --full → Same result

Error log from the backup status (sanitized for privacy)

Attempt of put Nr. 1 failed. S3UploadFailedError: Failed to upload /tmp/duplicity-t0s9y2bu-tempdir/mktemp-erbe5bku-83 to <s3-bucket-with-subfolder>/duplicity-inc.20250117T025009Z.to.20250118T005208Z.vol1.difftar.gpg: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.
Attempt of put Nr. 2 failed. S3UploadFailedError: Failed to upload /tmp/duplicity-t0s9y2bu-tempdir/mktemp-erbe5bku-83 to <s3-bucket-with-subfolder>/duplicity-inc.20250117T025009Z.to.20250118T005208Z.vol1.difftar.gpg: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.
Attempt of put Nr. 3 failed. S3UploadFailedError: Failed to upload /tmp/duplicity-t0s9y2bu-tempdir/mktemp-erbe5bku-83 to <s3-bucket-with-subfolder>/duplicity-inc.20250117T025009Z.to.20250118T005208Z.vol1.difftar.gpg: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.
Attempt of put Nr. 4 failed. S3UploadFailedError: Failed to upload /tmp/duplicity-t0s9y2bu-tempdir/mktemp-erbe5bku-83 to <s3-bucket-with-subfolder>/duplicity-inc.20250117T025009Z.to.20250118T005208Z.vol1.difftar.gpg: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.
Giving up after 5 attempts. S3UploadFailedError: Failed to upload /tmp/duplicity-t0s9y2bu-tempdir/mktemp-erbe5bku-83 to <s3-bucket-with-subfolder>/duplicity-inc.20250117T025009Z.to.20250118T005208Z.vol1.difftar.gpg: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.
Traceback (most recent call last):
  File "/root/mailinabox/management/backup.py", line 655, in <module>
    perform_backup(full_backup)
  File "/root/mailinabox/management/backup.py", line 322, in perform_backup
    shell('check_call', [
  File "/root/mailinabox/management/utils.py", line 127, in shell
    ret = getattr(subprocess, method)(cmd_args, **kwargs)
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/duplicity', 'incr', '--verbosity', 'warning', '--no-print-statistics', '--archive-dir', '/opt/mail/backup/cache', '--exclude', '/opt/mail/backup', '--exclude', '/opt/mail/owncloud-backup', '--volsize', '250', '--gpg-options', "'--cipher-algo=AES256'", '--allow-source-mismatch', '--s3-endpoint-url', 'https://s3.nl-ams.scw.cloud', '--s3-region-name', 'nl-ams', '/opt/mail', 's3://<s3-bucket-with-subfolder>']' returned non-zero exit status 50.

Does anyone have the same issue and provide some hint on how to fix this?

Thanks in advance!

Best regards
mgr

2

I am receiving the same error log. Duplicity itself has not been updated recently, so that cannot be the cause. The backup script is running automatically, but no new files are being backed up.

3

After Duplicity backups failed for two days, a backup ran successfully about 3 hours ago. The only change was upgrade of the Ubuntu vim, vim-common, vim-runtime, vim-tiny, and xxd software packages.

4

I checked all recent updates and i have still the issue with failing S3 uploads.

5

Same problem here since upgrade.
Reconfigured S3 backups with BackBlaze but still having this error.

Anyone find a solution ?

6

Nope, still have these issues

7

It looks like the S3 Provider did some changes and the backup mechanism is working again.

1 Like
8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.