is it a custom domain with cache?

yes

on the requests that are slow, do you get cf-cache-status: HIT ?

if so, please open a support ticket and let me know the ticket number, or let me know if you cant manage to open a ticket

hmm i did some more playing around and it seems like I can get normal speeds in incognito but not in the normal browser. it might also be because i'm using a different subdomain/bucket (but on the same domain). i'll open up a ticket if i can't work it out

@jlam incognito also disables your browser extensions…

I'm aware of that, but I'm confident adblock and other extensions weren't affecting it since I disabled them. I also noted the content served fine in the normal browser after it loaded in incognito. Maybe my internet just died

Credential access key has length 53, should be 32 ??? using Rclone ???

Do you by any chance have the

# some comment

on the same line as the access key in your file?

I remember there being something weird about a comment in the file and rclone

yeah 🙂 that was it 🙂 thanks

uploading some trained AI data and needed to use rclone for that so 🙂

pth files can become rather big

If you open a ticket feel free to let me know the ticket number so I can look into it - definitely shouldnt be seeing this if theres not something wrong on your end

Thanks Erisa, should be all good now. I'll let you know if I open a ticket

Hi there, I have issue with CORS using R2 Storage, I investigated this, looked all community forum threads and now I sure there are some issue in place. Use case: R2 Bucket on dedicated domain serving static files for website on another domain. It works except content loaded through css files

src: url(../webfonts/fa-solid-900.eot);

I prepared example Static content bucket: https://cors-test-static.quaded.com Website which use css and font from static bucket: https://cors-test-page.quaded.com/index.html Look devconsole. Meanwhile, this helped to fix issue, but obviously it is not best solution: https://community.cloudflare.com/t/problem-with-settings-cors-policies-on-r2/432339/18

Have you actually setup CORS on that bucket through the dashboard or S3 API & are having problems with that?

CORS isn’t enabled by default by any means

Hi @kian I configured CORS through the dashboard, current configuration is echoed on the example page (allowed all by wildcard, non-wildcard allowance also was in place).

CSS file loads correctly, but child assets not loads.

You know, by some reason it works now, but not worked this night when I worked to prepare example. Maybe some cache affected this. Hm... Anyway as you can see by community threads it's wide issue, maybe due to default CORS settings which getting cached?

Hi all! Hopefully someone can help me with this problem I'm having with range requests on a production workflow. The following request correctly respects the range header:

curl https://cdn-temp.urbanist.video/streaming-playlists/hls/3ef701af-04bb-4b63-9e53-a95e97a20463/177da0e8-5823-4702-bab2-5b7d6fd1b3d7-1440-fragmented.mp4 --header "Range: bytes=0-1330" -o out.mp4

But this one doesn't, and instead returns the entire object:

curl https://cdn-temp.urbanist.video/streaming-playlists/hls/3ef701af-04bb-4b63-9e53-a95e97a20463/43440bd2-e85b-4b49-9f10-3f6c56f09e8c-2160-fragmented.mp4 --header "Range: bytes=0-1330" -o out.mp4

Any help would be really appreciated! ❤️ Thank you!

Okay, so as a workaround I followed this: https://community.cloudflare.com/t/public-r2-bucket-doesnt-handle-range-requests-well/434221/4 and turned off caching for the r2 bucket public domain, so the above request now works fine. Obviously this isn't ideal. Cloudflare, please fix range requests for r2 buckets 🙂 Thank you

if turning off caching fixes it, could it be a general CDN cache issue rather than R2 specific?

reading the post now though

Yeah, based on the above thread it appears to be a general cf CDN issue. Also the range requests directly to the bucket work great

I see, that sounds less than ideal caching behaviour, would have thought it would return the range even if it does grab the whole file in the background

Yes 🙂 I have a hunch that because the 4k video is > 500mb, the range request is not respected when using a custom domain and cf proxies it

because the problem only occurs when trying to fetch the 2160p file (others are fine)

this is a known bug with the cache, when it serves a range request it first tries to obtain the full file, cache it and serve ranges from that