Hi, everyone,I would be happy to receive help with the problem I have with R2 (ticket number 323188
Hi, everyone,
I would be happy to receive help with the problem I have with R2 (ticket number 3231889)
Description of the fault:
Recently, we have been uploading encoded video files to R2 storage using the S3 API, and some of them are corrupted.
This is causing a certain percentage of our new VODs not to stream!
Are you aware of any issues?
What do you suggest we do to ensure the files are uploaded safely?
Picture of couple of bad video objects without meta data attached,
next to them others that are good, also same objects of AWS S3 are good.
We are using the PutObject command from the @aws-sdk library to upload files. Here's the code snippet:
const command = new PutObjectCommand({
Bucket: bucket,
Key: s3ObjectKey,
Body: stream,
ContentType: contentType,
ContentMD5: contentMD5,
});
const result = await client.send(command);
The customer added the Content-MD5 to detect and reupload corrupted uploads. They have observed that sometimes the MD5 hash is different, indicating issues during the transfer.
Below are some of the errors they have encountered:
2024-05-17T20:33:20.048Z ee39cf6c-a8e4-405e-a432-f44ddba817ca ERROR Error uploading files to cloudflare. file: 1705242326_raketa_1_480p.mp4 error message: UnknownError
2024-05-20T08:39:08.849Z 499da2bb-d8b1-4352-b418-d243f2e70ec3 ERROR Error uploading files to cloudflare. file: 2005241137_commando_480p.mp4 error message: UnknownError
#r2
4 Replies
So your uploads are failing?
About twenty percent of uploads fail.
We did not find a link to something uniform for all the uploads that fail except that after the upload fails we see that the hashing of MDM5 shows that there was a change in the file.
And we worked with this method for over a year without any malfunctions,
Maybe there was a change in API commands on the subject? Which could mean that the API command we use is not suitable for all cases?
I see
That's odd, let me escalate that ticket for you
Escalated
Thanks