It shouldn't, you can even visit it directly in your browser and just get an s3 error about no auth

It shouldn't, you can even visit it directly in your browser and just get an s3 error about no auth header. What's your account id (it's safe to share, nothing sensitive/anything you can do with it)
That behavior may make sense if there's no cert issued for it by CF, but there should be...

CChaika It shouldn't, you can even visit it directly in your browser and just get an s3 ...

petazz.•12/20/24, 7:31 PM

Ah ok trying it with the browser somehow triggered me. It seems I had a typo in my accountId. It's funny that's the symptom. You'd somehow expect to get a 404-type of message and not ERR_SSL_VERSION_OR_CIPHER_MISMATCH if the "resource" is not found

petazz.•12/20/24, 7:32 PM

Thanks for your help!

Ppetazz.Ah ok trying it with the browser somehow triggered me. It seems I had a typo in ...

ChaikaOP•12/20/24, 7:37 PM

It seems I had a typo in my accountId. It's funny that's the symptom. You'd somehow expect to get a 404-type of message and not ERR_SSL_VERSION_OR_CIPHER_MISMATCH if the "resource" is not found

It's because if you misspell it, Cloudflare doesn't have a certificate to cover the misspelling (no *.r2.cloudflarestorage.com), and ERR_SSL_VERSION_OR_CIPHER_MISMATCH is Cloudflare's way of conveying that it has no valid certificate to use (and thus openssl can't establish a connection either)

petazz.•12/20/24, 7:56 PM

Right, I just think it's quite rare to see so strict SNI enforcing. Which is good I guess

BlackForestBoi•12/21/24, 2:52 PM

Hey folks!

anyone experiencing not being able to subscribe to the R2 buckets?
For some unexplainable rason our R2 access was removed and I cannot resubscribe.
Everytime i try my page reloads and goes back to the same state.

Access to the bucket is not possible right now.

BBlackForestBoi Hey folks! anyone experiencing not being able to subscribe to the R2 buckets? ...

BlackForestBoi•12/21/24, 2:54 PM

Ok seems like quite a few people do that going by that thread. Has anyone gotten this resolved for them? Currently our users cannot access their data and I am afraid that at some point CF may delete the data. Our payment options are valid and funds available so I am not sure whats the problem.

Vi•12/21/24, 6:37 PM

Hey! I have a question regarding r2 and collecting logs. Basically, I serve a bunch of various files which users will be accessing via a cloudflare worker that'll return the specific object within r2. I want to keep track of the number of times each file was downloaded/viewed so one option would be to just update a download column in a db somewhere within my worker when a file is requested. However I worry that this may cause a bit of latency since I have to wait to open a db connection, update a record, wait for it to update, and I'm serving HLS files so the requests will be coming in pretty quickly. My next idea was to do see if I can forward the logs itself to an endpoint I've setup which removes the need to have any of this within the worker. First off, is this even possible, and secondly, would there still be a log forwarded even if the file was obtained through the cache rather than r2?

Or, is there a better way to go about all this? Open to all suggestions!

Vi•12/21/24, 6:41 PM

When a file is being served via the worker, don't we do something like return request(...) and since we're returning it, it'll exit out of the worker right? Meaning anything I put after that statement won't run

Vi•12/21/24, 6:47 PM

Right but isn't that still the same as doing it syncronously? Like the response will need to wait until the db finishes incrementing because otherwise it'll return the response and exit out before the db increment occurs right?

Vi•12/21/24, 6:50 PM

Maybe I'm misunderstanding how workers work but I thought this would be the "right" way to do it but it'll cause latency since we're waiting for the db.update method to run

await db.update...
return response(...)

because if we just do

db.update...
return response(...)

this will run async and since the db.update call runs in the method and not some sort of queue/background processor, when return response(...) finishes running the method/worker will close even if db.update is still running

That's how I'm thinking about it but I could be wrong

Vi•12/21/24, 6:59 PM

Oh wow this is very cool. I wrote some quick psuedo code but is this how it should behave?

export default {
  async fetch(request, env, ctx) {
    // Get the file
    let res = await fetch(request);

    // Do the db analytics
    ctx.waitUntil(await db.update(imaginary method to update db));

    // This will be immediately executed, then the worker will close once line above finishes
    return res;
  },
};

export default {
  async fetch(request, env, ctx) {
    // Get the file
    let res = await fetch(request);

    // Do the db analytics
    ctx.waitUntil(await db.update(imaginary method to update db));

    // This will be immediately executed, then the worker will close once line above finishes
    return res;
  },
};

Vi•12/21/24, 7:03 PM

Ah so something like this?

Vi•12/21/24, 7:03 PM

export default {
  async fetch(request, env, ctx) {
    // Get the file
    let res = await fetch(request);

    // Do the db analytics
    ctx.waitUntil(dbCall(request));

    // This will be immediately executed, then the worker will close once line above finishes
    return res;
  },
  async dbCall(request) {
    // Make a call to the DB and using the params in the request
    // find the file and update it
    await db.update(...)
  }
};

export default {
  async fetch(request, env, ctx) {
    // Get the file
    let res = await fetch(request);

    // Do the db analytics
    ctx.waitUntil(dbCall(request));

    // This will be immediately executed, then the worker will close once line above finishes
    return res;
  },
  async dbCall(request) {
    // Make a call to the DB and using the params in the request
    // find the file and update it
    await db.update(...)
  }
};

Vi•12/21/24, 7:03 PM

Oh yeah whoops

Vi•12/21/24, 7:04 PM

Okay dumb question but why isn't it async function fetch

Vi•12/21/24, 7:05 PM

actually won't making ctx.waitUntil(dbCall(request)); into ctx.waitUntil(this.dbCall(request)); make the code above work?

imf1xic•12/21/24, 9:15 PM

imf1xic•12/21/24, 9:15 PM

how i can fix it

Andreychik32•12/21/24, 11:43 PM

I have the same error as @imf1xic has.

imf1xic•12/21/24, 11:44 PM

yeah

imf1xic•12/21/24, 11:44 PM

i create a bucket with wrangler and r2 worked

imf1xic•12/21/24, 11:45 PM

https://developers.cloudflare.com/r2/buckets/create-buckets/

Cloudflare Docs

Create new buckets · Cloudflare R2 docs

You can create a bucket from the Cloudflare dashboard or using Wrangler.

Andreychik32•12/21/24, 11:46 PM

oh thanks, will try this

imf1xic•12/21/24, 11:46 PM

im russian, u can ask me dm

imf1xic•12/21/24, 11:46 PM

@Andreychik32

Andreychik32•12/21/24, 11:50 PM

I've created a bucket successfully using your method and now it correctly appears under overview. Thanks.

anxidashu•12/22/24, 1:37 AM

why TTFB is so long even cache is hit?

maneesh•12/22/24, 8:19 AM

hello everyone, i am maneesh from AdTip company from india, we are facing issue, our user data disapper in cloud fair, we don't know what is issue, please resolve it quickly.

maneesh•12/22/24, 8:21 AM

i would like talk cloud fair team, please connect with me @Cloudflare (Server Owner) team, i am waiting, we have lot of user, please resolve it quickly.

SuperHelpflare•12/22/24, 8:47 AM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

maneesh•12/22/24, 9:00 AM

@FloppyDisk

how will we resolve issue of cloud fair ?

maneesh•12/22/24, 9:14 AM

thanks i raised ticket

Mmaneesh hello everyone, i am maneesh from AdTip company from india, we are facing issue,...

Ghost Furry•12/22/24, 9:28 AM

Cloudflare R2 is still not ready to be used in production

Their support system sucks .. so best is always take the backups

anxidashu•12/22/24, 12:43 PM

@SpaceThanks, I realize this is a problem. But when I drop the proxy, it still connet to US server. I am located at China mainland. This image is stored in R2, default location is APAC.

anxidashu•12/22/24, 12:45 PM

Sorry, I though it will connet to the nearest server, maybe Tokyo or Hongkong, right?

anxidashu•12/22/24, 12:46 PM

I can give it a try, how to ?

anxidashu•12/22/24, 12:55 PM

ok, other than this, any chance to reduce latency?

anxidashu•12/22/24, 12:56 PM

how to ? any advice?

anxidashu•12/22/24, 1:02 PM

This is ... unexpected. You mean droping CDN can be even fater...

anxidashu•12/22/24, 1:05 PM

ok, i will try

maco6517•12/22/24, 3:29 PM

Does caching m3u8 files in r2 violate any rules?

bun•12/22/24, 5:29 PM

lmfao this button leads to https://developers.cloudflare.com/r2/api/workers/workers-api-usage/

Cloudflare Docs

Use R2 from Workers · Cloudflare R2 docs

C3 (create-cloudflare-cli) is a command-line tool designed to help you set up and deploy Workers & Pages applications to Cloudflare as fast as possible.

bun•12/22/24, 5:29 PM

on https://dash.cloudflare.com/ACC_ID/r2/overview

Bbun on https://dash.cloudflare.com/ACC_ID/r2/overview

bun•12/22/24, 5:33 PM

bun•12/22/24, 5:34 PM

bun•12/22/24, 5:36 PM

:hmm:

bun•12/22/24, 5:36 PM

no idea then

ianmateus•12/22/24, 6:30 PM

Is anyone having this problem?

ianmateus•12/22/24, 6:46 PM

okay thanks

Original message was deleted

Hard@Work•12/22/24, 7:04 PM

Do you have a list of reports? I can try passing it up

export default { async fetch(request, env, ctx) { // Get the file let res = await fetch(request); // Do the db analytics ctx.waitUntil(await db.update(imaginary method to update db)); // This will be immediately executed, then the worker will close once line above finishes return res; }, };

export default { async fetch(request, env, ctx) { // Get the file let res = await fetch(request); // Do the db analytics ctx.waitUntil(dbCall(request)); // This will be immediately executed, then the worker will close once line above finishes return res; }, async dbCall(request) { // Make a call to the DB and using the params in the request // find the file and update it await db.update(...) } };

It shouldn't, you can even visit it directly in your browser and just get an s3 error about no auth

Similar Threads

Similar Threads

Similar Threads