Can you use the same bucket name in

preview_bucket_name

? Trying to get local dev working for this worker, but I don't want to duplicate my files into a separate bucket.

Yep

Yeah, you can use the same bucket

I think theres a warning that recommends you not to (or maybe that was just KV), but if thats what you want you can just ignore it

So it works as far as running the command, but it doesn't seem like it has access to the actual files in the bucket.

Looks like you're using

--local

or

--experimental-local

there since it says Miniflare

Oh yeah, you are

Only normal

dev

is remote with access to the 'real' bucket

but it says only nodejs_compat works with experimental-local lol

Works in production fine

Just not

--local

I can't debug in production

So just remove

--experimental-local

?

Like I said,

dev

by default is remote

Thanks, that worked, I was under the impression that was required for nodejs_compat to work.

Hi, need help with setting up subdomain for R2. I purchased domain and I can set it for R2, but I want R2 to be on a subdomain. To do it, I must create subdomain first. But for subdomain creation I must provide IPv4 address. So how to do it?

It'll create the necessary DNS Record for you when you connect the domain in your bucket's settings

When I'm trying to connect new subdomain I'm getting "That domain was not found on your account."

Double check your input? What's the domain you are trying to connect?

(It has to be a domain/zone active in the same account)

Oh wow for regular domain I'm getting same message UPD somehow it just worked after next try

anyone know how to deal with CORS errors from R2 when using

fetch

for

GET

request with presigned url? Getting

No 'Access-Control-Allow-Origin' header is present on the requested resource.

I've tried all the stuff from https://developers.cloudflare.com/r2/buckets/cors/ and https://community.cloudflare.com/t/problem-with-settings-cors-policies-on-r2/432339... Settings are:

[
  {
    "AllowedOrigins": [
      "http://localhost:3000"
    ],
    "AllowedMethods": [
      "GET",
      "PUT",
      "HEAD"
    ],
    "ExposeHeaders": [
      "*"
    ],
    "MaxAgeSeconds": 2
  }
]

Is your fetch request setting an

Origin

header?

Origin

header cannot be set programmatically in javascript

it's even more confusing because sometimes it does return the correct headers some times it does not, with identical fetch calls

Clear your Cloudflare caches, perhaps

If it's happening sometimes

alright I'm pretty sure it's related to the fact that I'm rendering some image in an

<img/>

tag and also fetching that same image with

fetch

, and theres some weird browser side caching going on that makes it where when the

fetch

resolves it doesn't have the desired CORS header... this must be the case because if I generate a second presigned url that doesn't appear in any

<img/>

i don't get the CORS issue, nor do i see the issue if I try the same fetch from a different browser, also is fixed if I don't render an

<img/>

with that src IDK if this has anything to do with R2, i think it's just something chrome is doing. 🥲