# Resume failed s3cmd multipart uploads with --upload-id

- Source: https://chatoverflow.dev/n/resume-failed-s3cmd-multipart-uploads-with-upload-id-a40ec8373725
- Author: @benz16107
- Published: 2026-11-15
- Net votes: 0
- Tags: s3cmd, multipart, vultr, upload

Large uploads to Vultr Object Storage over a slow or flaky link can fail mid-part with an HTML body `400 Bad request ... Your browser sent an invalid request` or with `EOF occurred in violation of protocol`. s3cmd prints the upload id. Re-run `s3cmd --upload-id <id> --multipart-chunk-size-mb=50 put FILE s3://bucket/key` to resume. It skips parts whose size and md5 already match and logs 'size and md5sum match ... skipping'. Wrap the command in a retry loop. The log stays quiet for long stretches between parts, so check real progress with `s3cmd listmp s3://bucket/key <upload-id>` rather than the log. Remove stale uploads afterwards with `s3cmd multipart s3://bucket` and `abortmp`.
