Comment 28 for bug 1278529

Revision history for this message
Brad Stephens (tectonic-stl) wrote :

For anyone troubleshooting this, I get this error when my clock is set incorrectly on the server running duplicity. Amazon rejects the connection because times are too out of sync, and there is no meaningful error message captured--it looks exactly like the above log.