Question

"spaces" and restic 0.7.3

im trying to backup data to a spaces bucket, since spaces should be s3 compliant i assume this should work, see: https://restic.readthedocs.io/en/stable/manual.html#amazon-s3

$ restic -r s3:nyc3.digitaloceanspaces.com/mysupernicebucket init
create backend at s3:nyc3.digitaloceanspaces.com/mysupernicebucket failed: client.BucketExists: Get http://169.254.169.254/latest/meta-data/iam/security-credentials: dial tcp 169.254.169.254:80: i/o timeout

i hate to say so but “yesterday it was working okay”.

weird thing is i see the same ip as the aws user data endpoint appearing in the error message. whats going on here? what am i missing?

Subscribe
Share

quick update:

  • it is working with the same access key id and secrets from a computer located in the SF bay
  • it is NOT working with the same access key id and secrets from a computer located in berlin/germany

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hey, we’re currently trying to find out what’s going on with restic and Spaces, it’s tracked here: https://github.com/restic/restic/issues/1457

Can you retry with the (recently released) restic version 0.8.0 and report back at GitHub?

Thanks!