ERROR: S3 Service API: Unsupported header ‘x-amz-checksum-crc32’

(@neilgee)

Using version 5.0.7, and when backing up to BackBlaze B2 getting the error:


Starting upload to S3 Service …
[17-Mar-2025 10:23:26] ERROR: S3 Service API: Unsupported header 'x-amz-checksum-crc32' received for this API call.
[17-Mar-2025 10:23:26] 2. Trying to send backup file to S3 Service …
[17-Mar-2025 10:23:27] Connected to S3 Bucket "my-backups" in us-west-002
[17-Mar-2025 10:23:27] Checking for not aborted multipart Uploads …
[17-Mar-2025 10:23:28] Upload for wekidz/2025-03-17_10-22-47_LTEHRRLX01_FILE-DBDUMP-WPPLUGIN.tar aborted.
[17-Mar-2025 10:23:28] Starting upload to S3 Service …
[17-Mar-2025 10:23:28] ERROR: S3 Service API: Unsupported header 'x-amz-checksum-crc32' received for this API call.

With the older version 4 plugin this issue does not exist

Viewing 10 replies - 1 through 10 (of 10 total)

Plugin Support WPM Support
(@saranshwpm)

11 months, 3 weeks ago

Hi,

There has been no change in the code for the integration part, so if it is working on v4, it should work on v5 too.

Can you please try setting the integration again to see how it goes?

Best Regards,

Thread Starter neilgee
(@neilgee)

11 months, 3 weeks ago

Happening on multiple sites, integration is from scratch – I have to downgrade on so many sites

Thread Starter neilgee
(@neilgee)

11 months, 3 weeks ago

Can you please try a backup to Backblaze B2 via S3 connection.

Maybe BackWPUp v5 introduced changes to the S3 upload process, likely adding the x-amz-checksum-crc32 header by default. Since Backblaze B2 doesn’t support that, it’s causing the failure.
Thread Starter neilgee
(@neilgee)

11 months, 3 weeks ago
See image below –

Requests that include the following checksum HTTP headers are rejected with a 400 Bad Requestresponse:
- x-amz-checksum-crc32
- x-amz-checksum-crc32c
View post on imgur.com

Ref – https://www.backblaze.com/docs/cloud-storage-s3-compatible-api
Thread Starter neilgee
(@neilgee)

10 months, 3 weeks ago

@saranshwpm can you please look at my later postings in this thread as it shows the reason why this is happening

kpont
(@kpont)

10 months, 1 week ago

I’m experiencing this same issue backing up to B2 on the sites I’m using this plugin on.
“ERROR: S3 Service API: Unsupported header ‘x-amz-checksum-crc32’ received for this API call”

Plugin Support WPM Support
(@saranshwpm)

10 months, 1 week ago

Hi,

Sorry for the delay.

We’ve raised this to our developers, and it’s now under review. It appears to be related to an unsupported checksum header during the S3 API call with Backblaze B2. We’re hopeful this will be addressed in one of our future releases.

We appreciate your patience and understanding in the meantime!

Best regards,
The BackWPup Team
prossel
(@prossel)

10 months, 1 week ago
The same error occurs with DreamHost DreamObjects storage on their new cluster.
```
ERROR: S3 Service API: Unsupported header 'x-amz-checksum-crc32' received for this API call
```
Using BackWPup 5.2.1

Here is their answer:

Unfortunately this isn’t a matter of a configuration missing from the new US-East 5 cluster, but a design choice. Upload checksums like the kind provided by that header are no longer supported and will need to be disabled in order to continue uploading.

Looks like either DreamHost or BackWPup need to change something to fix the issue. They don’t seem to be willing.

Will you ?
Thread Starter neilgee
(@neilgee)

9 months, 3 weeks ago

Hey @saranshwpm, remarking this thread as unresolved as it still is unresolved.

I was hoping that version 5.2.2 had the fix but sadly no it does not.

Plugin Support WPM Support
(@saranshwpm)

9 months, 3 weeks ago

Hello,

It is still under investigation. I don’t have ETA but it will be soon fixed in one of the future updates.

Best Regards,

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘ERROR: S3 Service API: Unsupported header ‘x-amz-checksum-crc32’’ is closed to new replies.