New clue for the Fatal Failed: 400 - bad_request: Sha1 did not match data received

Thanks! I edited your post to make the command stand out a bit more and bold / italicize the difference.

I did some tests with a local destination backup (see below) but the end result is something’s going on (even with a local destination), but I couldn’t reliably replicate it.

If possible, can you do a test of --upload-throttle=1MB and see if it works for you?


I tried running a local backup with –throttle-upload=25KB and got a “Warning while running task xxxx” window with “Got 0 warning(s)” in it.

I then got 5 retries each on the following - both with Hash mismatch on file ... errors:

  • Get with file duplicati-20180308T213015Z.dlist.zip
  • Get with file duplicati-i6735436af81a45b5bbd68ef999a63514.dindex.zip

Eventually the log summary showed:

Errors: [ Failed to process file duplicati-20180308T213015Z.dlist.zip => Hash mismatch on file “C:\Users\Me\AppData\Local\Temp\dup-27b3c118-2f9b-4c7c-8909-167304175f1e”, recorded hash: DY0vKz/ezWIYCcQgMyptJiTv0+pGm3DSI8fkkfwwF9g=, actual hash F+sho+hzvVuCcTUlN5ysiPvrNbvCOXG1bv6MXJVpeR4=, Failed to process file duplicati-i6735436af81a45b5bbd68ef999a63514.dindex.zip => Hash mismatch on file “C:\Users\Me\AppData\Local\Temp\dup-ca215f22-fc0f-43ed-a11b-24f1ffff7330”, recorded hash: td/lx+agGcBffag2DR2REyqQJLfGTHb3NvbuEIxqiWI=, actual hash wQzF4oSFE0MmDQh7Wuapv2Z1ckzsMfjslDap8D15qB4= ]


Here are some more results:

  • --throttle-upload=25000 → ERRORS (aka ~25KB but in bytes)
  • --throttle-upload=50KB → ERRORS
  • --throttle-upload=1024KB → ERRORS 50% of the time (aka 1MB but in KB)
  • --throttle-upload=2048KB → no errors (aka 2MB but in KB)
  • --throttle-upload=5120KB → no errors (aka 5MB but in KB)
  • --throttle-upload=10240KB → no errors (aka 10MB by in KB)
  • --throttle-upload=1048576KB → no errors (aka 1GB but in KB)
  • --throttle-upload=1MB → no errors
  • --throttle-upload=25GB → no errors
  • --throttle-upload=25TB → no errors

Note that in all cases with errors they came during the “Verifying …” step - so your backups are working just fine, it’s the verification step that’s failing.