We had a similar issue locally, with our backups on AWS S3. Turns out that current time for our local dev boxes had drifted out of sync with the actual time just enough for AWS to reject the requests.
Once we rebooted our box, everything worked fine. Obviously in a production environment, you can install and use something like ntp to keep your server(s) synched. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278529 Title: Using S3, "BackendException: No connection to backend" To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1278529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
