Sure, I can add multiple logs and check it out and get back to you on that. Something that pinged my

D

devrunnerOP•1/23/24, 12:30 PM

Based on what Ace mentioned, I thought there weren't any.

Ddevrunner Sure, I can add multiple logs and check it out and get back to you on that. Some...

H

Hello, I’m Allie!•1/23/24, 12:31 PM

The 1k requests that they are talking about are the API Ratelimits(afaict), which wouldn't apply here, since you are using the Workers APIs. They should be able to handle substantially higher rates of throughput

H

Hello, I’m Allie!•1/23/24, 12:31 PM

The API Ratelimits only apply to requests hitting

api.cloudflare.com

api.cloudflare.com

D

devrunnerOP•1/23/24, 12:32 PM

Ah alright, so that shouldn't apply to me since I have connected my worker to a custom domain.

D

devrunnerOP•1/23/24, 12:32 PM

I will use the wrangler to tail my worker and add a few extra errors to let you know.

D

devrunnerOP•1/23/24, 12:32 PM

I don't think the image merging is erroring though.

Ddevrunner Ah alright, so that shouldn't apply to me since I have connected my worker to a ...

H

Hello, I’m Allie!•1/23/24, 12:33 PM

It's more that you are(hopefully) using the R2 bindings in Workers, which aren't subject to the same(if any) rate-limiting

H

Hello, I’m Allie!•1/23/24, 12:33 PM

That should apply even if you use

workers.dev

workers.dev

workers.dev

workers.dev

D

devrunnerOP•1/23/24, 12:34 PM

I am using the bindings, alright, I'll tag you when I have a few logs.

T

Tony Leung•1/23/24, 3:06 PM

hi guys, has anyone tried yugabyte db with cf workers? Is its performance better than D1 or PlanetScale? Since D1 does not handle table altering and typing really well, D1 also does not have local backup (although the alpha backend had it) and can't natively integrate with external service so I'm considering switching to MySQL and Postgres

HHello, I’m Allie!It's more that you are(hopefully) using the R2 bindings in Workers, which aren't...

D

devrunnerOP•1/23/24, 3:36 PM

So, if I make the requests on their own they don't exceed the cpu time, which is the error thrown (which is set at 5kms for this testing). When I am making the requests in batches of 20 or more though, then the requests towards the end start failing. They should have their own 5kms limit though as they are new requests which they don't even come close to.

Below are some examples from various logs:

Request 1
(log) Got request: 1706022283145
(log) Passed Checks: 1706022283145
(log) Got Images from R2 using GET: 1706022284067
(log) Merge Started: 1706022284067
(log) Merge Finished: 1706022284067
(log) Put Images in R2: 1706022285188

~2000ms

Request 1
(log) Got request: 1706022283145
(log) Passed Checks: 1706022283145
(log) Got Images from R2 using GET: 1706022284067
(log) Merge Started: 1706022284067
(log) Merge Finished: 1706022284067
(log) Put Images in R2: 1706022285188

~2000ms

Request 1
(log) Got request: 1706022283145
(log) Passed Checks: 1706022283145
(log) Got Images from R2 using GET: 1706022284067
(log) Merge Started: 1706022284067
(log) Merge Finished: 1706022284067
(log) Put Images in R2: 1706022285188

~2000ms

Request 1
(log) Got request: 1706022283145
(log) Passed Checks: 1706022283145
(log) Got Images from R2 using GET: 1706022284067
(log) Merge Started: 1706022284067
(log) Merge Finished: 1706022284067
(log) Put Images in R2: 1706022285188

~2000ms

Request 2
(log) Got request: 1706023000944
(log) Passed Checks: 1706023000944
(log) Got Images from R2 using GET: 1706023002066
(log) Merge Started: 1706023002066
(log) Merge Finished: 1706023002066
(log) Put Images in R2: 1706023003270

~2300ms

Request 2
(log) Got request: 1706023000944
(log) Passed Checks: 1706023000944
(log) Got Images from R2 using GET: 1706023002066
(log) Merge Started: 1706023002066
(log) Merge Finished: 1706023002066
(log) Put Images in R2: 1706023003270

~2300ms

Request 2
(log) Got request: 1706023000944
(log) Passed Checks: 1706023000944
(log) Got Images from R2 using GET: 1706023002066
(log) Merge Started: 1706023002066
(log) Merge Finished: 1706023002066
(log) Put Images in R2: 1706023003270

~2300ms

Request 2
(log) Got request: 1706023000944
(log) Passed Checks: 1706023000944
(log) Got Images from R2 using GET: 1706023002066
(log) Merge Started: 1706023002066
(log) Merge Finished: 1706023002066
(log) Put Images in R2: 1706023003270

~2300ms

Same images, just another request

// Errored
Request 3
(log) Got request: 1706022678022
(log) Passed Checks: 1706022678022
(log) Got Images from R2: 1706022678938
(log) Merge Started: 1706022678938

~900ms

// Errored
Request 3
(log) Got request: 1706022678022
(log) Passed Checks: 1706022678022
(log) Got Images from R2: 1706022678938
(log) Merge Started: 1706022678938

~900ms

// Errored
Request 3
(log) Got request: 1706022678022
(log) Passed Checks: 1706022678022
(log) Got Images from R2: 1706022678938
(log) Merge Started: 1706022678938

~900ms

// Errored
Request 3
(log) Got request: 1706022678022
(log) Passed Checks: 1706022678022
(log) Got Images from R2: 1706022678938
(log) Merge Started: 1706022678938

~900ms

D

devrunnerOP•1/23/24, 3:36 PM

Is there a limit somewhere that I need to update?

U

Unsmart•1/24/24, 4:04 AM

I don’t think those specific limits will be changed tbh

S

Sz•1/24/24, 10:07 AM

Hey, is there a recommended way to protect workers with api keys? I'm fairly new to API gateways as a whole and saw that cloudflare offers an API gateway through shield, but it's only available to enterprise clients

Was wondering if there was a way to setup a separate worker to act as a proxy and for handling api key management while storing the api keys in KV storage

S

Sz•1/24/24, 10:08 AM

Also came across this post on reddit that talked about how to implement just that, but it goes really in depth
https://www.reddit.com/r/CloudFlare/comments/194r1kx/cloudflare_worker_review_api_key_service/

From the CloudFlare community on Reddit: Cloudflare Worker Review: ...

Explore this post and more from the CloudFlare community

X

X•1/24/24, 11:32 AM

thanks

X

X•1/24/24, 11:39 AM

wow

K

kev-ac•1/24/24, 2:43 PM

Don't know if it is a better fit here or in #r2: I noticed that one of my workers started to throw errors since 2023-12-24. What I figuered out is that out of nowhere the R2 binding to this worker does not work anymore. It is a binding to a EU-jurisdiction bucket. I've not touched the bucket or worker prior to today for 2 months.

The binding is still visible in the UI but I get

The specified bucket does not exist. (Code: 10006)

The specified bucket does not exist. (Code: 10006)

The specified bucket does not exist. (Code: 10006)

The specified bucket does not exist. (Code: 10006) errors. I've tried re-assigning the bucket to the worker but it is not even showing up in the list of buckets (no EU-jurisd. buckets do).

Is this a known issue or something that has changed in the workers platform I did not notice?

Kkev-ac Don't know if it is a better fit here or in #r2: I noticed that one of my worker...

C

Cyb3r-Jak3•1/24/24, 2:45 PM

Have you raised this on community forums? Or first time

CCyb3r-Jak3 Have you raised this on community forums? Or first time

K

kev-ac•1/24/24, 2:46 PM

No I haven't, haven't used the forums in a while. Most times I stumble across a community forum post via google it is unresolved with no answer at all... On the other hand here is (mostly) always someone to help or give a hint in the right direction.

Kkev-ac Don't know if it is a better fit here or in #r2: I noticed that one of my worker...

C

Chaika•1/24/24, 2:48 PM

Did you publish the worker via wrangler to start with/try wrangler now?
The Jurisdiction docs only mention it being possible to bind to a eu bucket via wrangler and the jurisdiction param
https://developers.cloudflare.com/r2/reference/data-location/#using-jurisdictions-from-workers

Data location · Cloudflare R2 docs

Learn how the location of data stored in R2 is determined and about the different available inputs that control the physical location where objects in …

CChaika Did you publish the worker via wrangler to start with/try wrangler now? The Juri...

K

kev-ac•1/24/24, 2:49 PM

It is deployed via wrangler and has the jurisdiction param. It has worked fine since october

Kkev-ac It is deployed via wrangler and has the jurisdiction param. It has worked fine s...

C

Chaika•1/24/24, 2:51 PM

ah ok makes sense then, I don't think it ever displayed right in the UI then/let you pick it from there.
If you wrangler tail, what's the exact error its throwing? It might be helpful to just try redeploying it as well

CChaika ah ok makes sense then, I don't think it ever displayed right in the UI then/le...

K

kev-ac•1/24/24, 2:51 PM

Can I trigger a schedule event via wrangler? Otherwise I have to wait for the next scheduled run to happen

C

Chaika•1/24/24, 2:53 PM

In Dev you can, not in prod. In prod your best bet is to make a secret endpoint which calls the scheduled event

K

kev-ac•1/24/24, 2:56 PM

Re-deploying seems to have fixed it. But: Something must have happened on 2023-12-24 that caused the binding to stop working. Maybe someone from CF might be interested in it.

Kkev-ac Re-deploying seems to have fixed it. But: Something must have happened on 2023-1...

C

Chaika•1/24/24, 2:58 PM

yea that's weird. I don't see anything on Workers or R2 change log around that date.
Do you have any deployments for that worker (under the deployments tab) on that date? Or was the last time you modified it before that?

CChaika yea that's weird. I don't see anything on Workers or R2 change log around that d...

K

kev-ac•1/24/24, 3:00 PM

No, nothing. Last deployment before the issue started was on 2023-11-17. Even had a look at my audit log to see if something happened at all, nothing.

K

kev-ac•1/24/24, 3:05 PM

Oh, I see that on 2023-12-23 various certificates related to the worker were renewed. Both

*.{worker-name}.{subdomain}.workers.dev

*.{worker-name}.{subdomain}.workers.dev

*.{worker-name}.{subdomain}.workers.dev

*.{worker-name}.{subdomain}.workers.dev and

*.{zone-domain}.tld

*.{zone-domain}.tld

*.{zone-domain}.tld

*.{zone-domain}.tld.

SSz Hey, is there a recommended way to protect workers with api keys? I'm fairly new...

D

dave•1/24/24, 4:42 PM

We use Cloudflare Access to protect Workers that only have a few users (usually 1-2).

U

Unsmart•1/24/24, 10:15 PM

You can talk with sales about your use case and see if its something they can increase limits on.

D

dave•1/25/24, 12:44 AM

Why do all my Workers show as

Last modified 7 days ago

Last modified 7 days ago

Last modified 7 days ago

Last modified 7 days ago now?

D

dave•1/25/24, 12:44 AM

when I actually click them, I see the last deployment was months ago

Ddave Why do all my Workers show as `Last modified 7 days ago` now?

C

Chaika•1/25/24, 12:46 AM

Did you perhaps migrate to Standard recently?

C

Chaika•1/25/24, 12:46 AM

I think that caused that.. if i remember right?

CChaika Did you perhaps migrate to Standard recently?

D

dave•1/25/24, 12:46 AM

yes, but I thought it was more than a week ago

CChaika Did you perhaps migrate to Standard recently?

D

dave•1/25/24, 12:47 AM

does that show up in the audit logs?

C

Chaika•1/25/24, 12:48 AM

I have no idea sorry, didn't check at the time and way too long ago now

D

dave•1/25/24, 12:50 AM

hmm you're probably right

D

dave•1/25/24, 12:52 AM

Is there a notification like this, but for Workers?

D

dave•1/25/24, 1:27 AM

Can you have multiple Tail Workers attached to a single Worker?

C

charl.dev•1/25/24, 4:53 AM

With smart placement, I have a worker with it enabled that proxies fetch requests from a Page function that is bound to it.
The proxy then calls our azure endpoints which are in EU. We do cname our host name e.g. api.example.com to azure via CF. I have made a few hundred requests however placement is still local. Is there no way to manually assign location?

R

Rahul Raikwar•1/25/24, 9:40 AM

How can solve this issue

M

Mitya•1/25/24, 10:38 AM

Is there a way to use the Wrangler GH Action to publish different branches to different environments of the same worker? Or is it easier to just set up a stage worker and a live worker?

K

kian•1/25/24, 10:40 AM

You can pass an environment but it has to already exist in Wrangler.toml

M

Mitya•1/25/24, 10:41 AM

Aha so you mean as long as I have stage and live set up as envs in the TOML, I can then configure the Action to push one branch to one env and another branch to the other?

K

kian•1/25/24, 10:41 AM

Yep

Sure, I can add multiple logs and check it out and get back to you on that. Something that pinged my

Similar Threads