R2 doesn't really have a concept of region-based "locations". You can hint a region you want your bu

R2 doesn't really have a concept of region-based "locations". You can hint a region you want your bucket to be created in, but that is it.

HHard@Work R2 doesn't really have a concept of region-based "locations". You can hint a reg...

GooningChatter•11/21/24, 5:04 PM

the region hint can still mean the bucket may land in any colo in ENAM that supports R2

GGooningChatter the region hint can still mean the bucket may land in any colo in ENAM that supp...

Hello, I’m Allie!•11/21/24, 5:07 PM

Yeah, sorry, I just meant that we don’t provide an outward-facing way of determining what colo your bucket is created in, nor do we provide any guarantees that the bucket will stay in that particular colo

Hello, I’m Allie!•11/21/24, 5:08 PM

The only guarantees provided are with Jurisdictions, where buckets created within a jurisdiction will always spawn in colos supported by said jurisdiction

GooningChatter•11/21/24, 5:10 PM

Fair enough ! That's what I needed to hear, thanks

GemsFord•11/21/24, 5:24 PM

Hello everyone, I’m new here.
I started using R2 a few months ago. I knew it had a free tier, but I later realized I wasn’t getting charged for my R2 usage. I didn’t think much about it when invoices weren’t being generated.

Now, I’ve reached a point where I have around 1TB of files stored and millions of operations. I’m worried that if I contact support, they might terminate my account due to this billing glitch or issue a pending bill for the last 8 months.

The other option I’m considering is migrating all the files to a new Cloudflare account without this subscription glitch.

Has anyone else faced a similar issue before?

tezcan•11/21/24, 5:29 PM

A little hint about R2. Cloudflare calculates the data size in R2 as decimal, not binary. So every 1 tb of data you upload will be calculated as 1.09 TB. Yes, I uploaded about 10 tb (the size shown in Linux) and it shows 10.99 TB. I will pay 15$ more

GemsFord•11/21/24, 5:34 PM

I will better create a backup of data to another account and then will reach the support (via email or ticket)

Original message was deleted

Hello, I’m Allie!•11/21/24, 5:36 PM

It shouldn’t. It is more just that it may not always exist in the same colo, but it should stay within that region

Original message was deleted

GemsFord•11/21/24, 5:37 PM

I can't check the stats of my r2 bucket for last 8 months, what if I have a huge bill to pay. I run a SaaS platform, and I mis-calculated my expenses. I may end up in a loss.

GemsFord•11/21/24, 5:43 PM

last 7 days

GemsFord•11/21/24, 5:45 PM

yeah around 30 * 8 = 240$

GemsFord•11/21/24, 5:45 PM

well that's not huge

GemsFord•11/21/24, 5:45 PM

thanks mate

Matt•11/21/24, 9:18 PM

This is your daily "I don't understand CORS post". We deployed a static asset to R2 fetched in JS by our site. It was failing when deployed on cors headers so I added a catch all to allow all origins

Unfortunately for some reason this broke my ability to access it from localhost

avatar:1  Access to XMLHttpRequest at 'https://thumbnails.r2.allout.game/playercharacter-21.json' from origin 'http://localhost:3010' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values 'http://localhost:3010, *', but only one is allowed.

avatar:1  Access to XMLHttpRequest at 'https://thumbnails.r2.allout.game/playercharacter-21.json' from origin 'http://localhost:3010' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values 'http://localhost:3010, *', but only one is allowed.

So I added a rule to not include my local IP in this cors rule. Is there any way to do this better so I don't have to keep rotating my local IP in this rule to access it while developing?

Flare•11/21/24, 9:19 PM

Troubleshooting 403 / CORS issues with R2

So, your assets aren't loading because you are getting a CORS error despite having setup everything correctly?
Let's try troubleshooting.

In your browser console, do you see a 401/403 error right above the CORS error? If yes, then you aren't actually dealing with a CORS issue! If you do have a CORS issue, head to the last section.

If you are using a Custom domain

Go to the Network tab and find the failing request (you may need to reload the page, since only requests after opening the developer tools are logged).
You need to check the response headers for the following two headers:

cf-cache-statuscf-cache-status
cf-mitigatedcf-mitigated

### If you have a cf-mitigatedcf-mitigated header

Your request was blocked by one of your WAF rules. Go to Security Events and look for what service blocked your request.

If you don't have a `cf-cache-statuscf-cache-status` header

Your request was blocked by Hotlink Protection.
Go to your dashboard and disable it or write a configuration rule to only disable on your Custom domain

If you are using the S3 API

Your request is very likely incorrectly signed.
Try executing the request via curl to inspect the real response returned by the S3 api and then tackle that issue.
Once your request is correctly signed, you'll receive the proper CORS headers.

If it's actually CORS

Here are some common issues with CORS configurations:

ExposeHeadersExposeHeaders is missing headers like ETagETag
AllowedHeadersAllowedHeaders is missing headers like AuthorizationAuthorization or Content-TypeContent-Type
AllowedMethodsAllowedMethods is missing methods like POSTPOST/PUTPUT (you do not need to include OPTIONSOPTIONS)

Matt•11/21/24, 9:20 PM

I've read through this post and none of the "non cors" paths are hitting. And the "actually cors" section doesn't seem relevant to this error

MMatt This is your daily "I don't understand CORS post". We deployed a static asset to...

Barry_Based_Benson•11/21/24, 9:24 PM

What does your cors config look like on r2

Matt•11/21/24, 9:37 PM

TIL there there is direct R2 cors config...

Matt•11/21/24, 9:45 PM

nice, moving the config there worked

Matt•11/21/24, 9:45 PM

ty!

boldpix•11/22/24, 6:48 PM

Do we need programming knowledge to setup R2/S3?

Whimsy•11/23/24, 9:34 AM

does r2 support lifecycle rules? like delete files after xyz, that match certain prefix

Whimsy•11/23/24, 10:39 AM

is this correct way to do so? cuz like idk it doesnt delete them

Niko•11/23/24, 10:43 AM

Hi! I've been trying to successfully load and play large (300MB-few GB's) files on Safari from R2. While it works perfectly fine on Chromium browsers, safari doesn't load media file.

In network tab I see requests failing.

I tried everything I could find. Bypassing the cache on cloudflare, other stuff found on Cloudflare's Blog.
https://community.cloudflare.com/t/videos-on-website-dont-play-only-affects-ios-users/569261
https://community.cloudflare.com/t/mp4-wont-load-in-safari-using-cloudflare/10587/56

File url: https://cdn.reinspire.io/media/b54e56f3-5ede-4eb3-bb73-60dda6d22c4f

Niko•11/23/24, 10:48 AM

codec_name=av1
codec_type=video
codec_name=aac
codec_type=audio

Niko•11/23/24, 10:50 AM

Okay thanks, I'll try the codecs mentioned above.

Will update here

Niko•11/23/24, 5:59 PM

@Space
File url: https://cdn-staging.reinspire.io/media/avc1-output-2.mp4

codec_name=h264
codec_type=video
codec_name=aac
codec_type=audio

Still can't play. Am I doing smth wrong here

Niko•11/23/24, 6:00 PM

Niko•11/23/24, 6:03 PM

hmmm, how do you test it?

I use vidstack player and it doesn't load file

Niko•11/23/24, 6:08 PM

normal playback works for me too, will experiment with diff players.

I am considering to switch to hls or cloudflare stream thing in future, but now can't do so.

Also any idea why do some range requests fail while others succeed. Looks weird to me

Niko•11/23/24, 6:11 PM

first one is always 2 bytes to test if server supports range request. Here's last one that succeeded with bigger content-length

Niko•11/23/24, 6:21 PM

Hmmm, yeah it works now if I use it like this:
So it's the player thing.

<video
  src="https://cdn-staging.reinspire.io/media/avc1-output-2.mp4"
  controls
>
  Your browser does not support the video tag.
</video>

<video
  src="https://cdn-staging.reinspire.io/media/avc1-output-2.mp4"
  controls
>
  Your browser does not support the video tag.
</video>

Thanks for the help, will explore different players

qu6it•11/23/24, 7:08 PM

Hi,

I'm new to R2 and attempting to integrate with the API. I've written a Node.js script to generate the Authorization header and x-amz-date, and I’ve included the host header as follows:

Headers:
Authorization: AWS4-HMAC-SHA256 Credential=xxxxxx/20241123/default/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=xxxxx
x-amz-date: 20241123T173455Z
Host: https://[accountId].r2.cloudflarestorage.com/[bucketName]

Endpoint:
The URL is constructed as follows, using the PUT HTTP method:
https://[accountID].r2.cloudflarestorage.com/[bucketName]/[objectKey]

When I send the request, I’m encountering the following error:
Error: write EPROTO 1185412057536:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../../../src/third_party/boringssl/src/ssl/tls_record.cc:592:SSL alert number 40

I’m wondering if this issue might be related to Cloudflare configuration, such as TLS settings, endpoint restrictions, or something else specific to R2.

Here are a few key details:

I’ve verified that the x-amz-date and Authorization headers are generated based on AWS Signature Version 4 (SigV4) - at least I think I have!!
The x-amz-content-sha256 is set to UNSIGNED-PAYLOAD.
My TLS environment supports versions up to 1.3.
This happens in multiple environments including when using Postman

Has anyone encountered this before?

Whether there are specific configurations or security settings in Cloudflare R2 that might cause this error?
Any additional debugging steps or requirements for establishing the TLS handshake with R2?

Any help would be greatly appreciated!

Original message was deleted

James•11/23/24, 11:27 PM

How often are you reading these files? R2 would work fine, but you might consider KV if the read performance of these is critical https://developers.cloudflare.com/kv/

Original message was deleted

Chaika•11/24/24, 1:08 AM

Why do you think you need so many namespaces? A namespace in KV is just a collection of keys and their values, essentially the same as an R2 bucket. Within each namespace, just like within each bucket, you have Keys (Object Keys in R2) and Values, also both R2 and KV can have metadata alongside as well. If you're doing everything within a single r2 bucket now, you can do it all within a single kv namespace

Original message was deleted

Hello, I’m Allie!•11/24/24, 1:23 AM

No, for example, you could have 23-11-2024 as the key, and your JSON as the value

Hello, I’m Allie!•11/24/24, 1:24 AM

That scales basically as far as you are willing to pay

Chaika•11/24/24, 1:34 AM

if it's still confusing: think of a namespace exactly as an r2 bucket, you throw a bunch of objects (Key-values) into it, each with a unique key/object key. Same structuring as with R2

埃

埃菲尔铁塔•11/24/24, 6:08 AM

Hi all, how will r2 be converted to infrequently accessed buckets after creating a standard bucket, I'm worried that my storage will be automatically converted to infrequently accessed buckets after a period of inaccessibility.

埃埃菲尔铁塔 Hi all, how will r2 be converted to infrequently accessed buckets after creating...

Hello, I’m Allie!•11/24/24, 6:14 AM

It won’t happen automatically, if that is what you mean

Hello, I’m Allie!•11/24/24, 6:14 AM

Infrequent Access will only be applied if you create a rule for it

埃

埃菲尔铁塔•11/24/24, 6:15 AM

I just read somewhere else someone complaining about this who said he seems to have been converted to paying for infrequent access to buckets because of infrequent access to buckets

埃埃菲尔铁塔 I just read somewhere else someone complaining about this who said he seems to h...

Hello, I’m Allie!•11/24/24, 6:18 AM

If it does happen without your input, that would be a pretty major bug, and should be reported

R2 doesn't really have a concept of region-based "locations". You can hint a region you want your bu

Troubleshooting 403 / CORS issues with R2

If you are using a Custom domain

If you don't have a `cf-cache-statuscf-cache-status` header

If you are using the S3 API

If it's actually CORS

Similar Threads

Similar Threads

Troubleshooting 403 / CORS issues with R2

If you are using a Custom domain

If you don't have a
`cf-cache-status`
`cf-cache-status`
`cf-cache-status`
`cf-cache-status` header

If you are using the S3 API

If it's actually CORS

Similar Threads

R2 doesn't really have a concept of region-based "locations". You can hint a region you want your bu

Troubleshooting 403 / CORS issues with R2

If you are using a Custom domain

If you don't have a cf-cache-statuscf-cache-status header

If you are using the S3 API

If it's actually CORS

Similar Threads

Similar Threads

Troubleshooting 403 / CORS issues with R2

If you are using a Custom domain

If you don't have a cf-cache-statuscf-cache-statuscf-cache-statuscf-cache-status header

If you are using the S3 API

If it's actually CORS

Similar Threads

If you don't have a `cf-cache-statuscf-cache-status` header

If you don't have a
`cf-cache-status`
`cf-cache-status`
`cf-cache-status`
`cf-cache-status` header