payloadcms/storage-s3: ERROR: Header 'x-amz-checksum-crc32' with value "" not implemented | Payload | Page 1

plush dust Jan 16, 2025, 9:41 PM

#

I removed the value because I have no idea if that is a security issue or not. I updated to 3.17.1, and now Cloudflare R2 storage is no longer working. This was "just working" and I am not sure how I messed anything up. My ask is: is anyone else seeing this error?

candid tendonBOT Jan 16, 2025, 9:41 PM

#

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

plush dust Jan 17, 2025, 3:16 PM

#

Copied from the thread in general chat

#

I am using Cloudflare R2 for S3 compatible bucket storage for images

#

https://developers.cloudflare.com/r2/api/s3/api/ and search "x-amz-checksum-algorithm"

Cloudflare Docs

S3 API compatibility · Cloudflare R2 docs

R2 implements the S3 API to allow users and their applications to migrate with ease. When comparing to AWS S3, Cloudflare has removed some API operations' features and added others. The S3 API operations are listed below with their current implementation status. Feature implementation is currently in progress. Refer back to this page for updates...

#

You can see they have no implemented a lot, if any, of the checksum "stuff"

#

So it looks like R2 is a poor choice on compatibility? And the answer is to find a different service.

#

Even though this was working in the past.

#

Actually thank you to @floral schooner for this: https://developers.cloudflare.com/r2/examples/aws/aws-sdk-js-v3/

Cloudflare Docs

aws-sdk-js-v3 · Cloudflare R2 docs

You must generate an Access Key before getting started. All examples will utilize access_key_id and access_key_secret variables which represent the Access Key ID and Secret Access Key values you generated.

#


Client version 3.729.0 introduced a modification to the default checksum behavior from the client that is currently incompatible with R2 APIs.

To mitigate, users can use 3.726.1 or add the following to their S3Client config:

requestChecksumCalculation: "WHEN_REQUIRED",
responseChecksumValidation: "WHEN_REQUIRED",```

floral schooner Jan 17, 2025, 3:22 PM

#

Nice, they gave a proper version to revert to

plush dust Jan 17, 2025, 3:23 PM

#

    s3Storage({
      collections: {
        media: true,
      },
      bucket: process.env.S3_BUCKET,
      config: {
        endpoint: process.env.S3_ENDPOINT,
        credentials: {
          accessKeyId: process.env.S3_ACCESS_KEY_ID,
          secretAccessKey: process.env.S3_SECRET_ACCESS_KEY,
        },
        region: process.env.S3_REGION,
        // ... Other S3 configuration
                requestChecksumCalculation: "WHEN_REQUIRED",
                responseChecksumValidation: "WHEN_REQUIRED",
      },
    }),
  ],```

#

Confirmed working and fixed

candid tendonBOT Jan 17, 2025, 3:24 PM

#

Payload Bot

Thread Solved!

Glad your issue was resolved! :tada: If you want to help make payload better, please give us a :star: on GitHub and review us - It helps us a lot.

🌟 Star Us on GitHub

Click here to star us on GitHub

👍 Review Us

Click here to review us on G2

floral schooner Jan 17, 2025, 3:24 PM

#

Sensational, my friend, I'm relieved

plush dust Jan 17, 2025, 3:24 PM

#

Well thank you for finding that.

#

I am relieved as well. I did not want to spend today finding and implementing a new cloud storage plugin

floral schooner Jan 17, 2025, 3:25 PM

#

Trust me, I was sweating as well

#payloadcms/storage-s3: ERROR: Header 'x-amz-checksum-crc32' with value "" not implemented

Documentation: