I am on a Worker paid plan, can't open a support ticket? The support page ask to upgrade the websi

I am on a Worker paid plan, can't open a support ticket?

The support page ask to upgrade the website, but I don't need a website. Just worker paid is enough

Omar Abid•11/9/24, 11:23 AM

is deploying workers down for anyone?

VVikash I am on a Worker paid plan, can't open a support ticket? The support page ask ...

Cyb3r-Jak3•11/9/24, 1:55 PM

Correct. You need a paid zone to be able to open tickets. Everyone is able open Account, billing and registrar tickets.

OOmar Abid is deploying workers down for anyone?

Walshy•11/9/24, 3:23 PM

What are you seeing?

samsung•11/9/24, 7:49 PM

If I am using Workers Websocket without Durable Objects (for example using it for listening to queues or as a proxy for another websocket server), how would the pricing work? Is it charged based on per request (hence per websocket connection) and the cpu-time used to process the websocket messages?

Ssamsung If I am using Workers Websocket without Durable Objects (for example using it fo...

fry69•11/9/24, 8:01 PM

Both CPU time and per Worker request (not subrequests the worker does)

samsung•11/9/24, 8:02 PM

Max of 30 seconds of CPU time per invocation - is this happening on the websocket ?

Ssamsung Max of 30 seconds of CPU time per invocation - is this happening on the websocke...

Isaac McFadyen•11/9/24, 8:04 PM

Yes. But keep in mind this is CPU time, not wall time (not time as measured on a clock but time that is measured based on how much compute you are doing)

Isaac McFadyen•11/9/24, 8:04 PM

I also believe a Websocket message resets that limit? (someone would have to confirm though)

fry69•11/9/24, 8:07 PM

Websockets seem to have indeed a very long or infinite timeout if I read this correctly -> https://community.cloudflare.com/t/how-can-i-use-a-worker-for-real-time-stuff-limits/325031/2?u=fry69

samsung•11/9/24, 8:17 PM

Okay, I tested it, it stays longer than 30 seconds. a 2-minute connection was provided.

Ssamsung Okay, I tested it, it stays longer than 30 seconds. a 2-minute connection was pr...

Isaac McFadyen•11/9/24, 8:22 PM

30 seconds is cpu time.

Isaac McFadyen•11/9/24, 8:22 PM

Let me see, I believe I had a tag for this.

Isaac McFadyen•11/9/24, 8:22 PM

?cpu-time

Flare•11/9/24, 8:22 PM

CPU Time: the amount of work the CPU needs to do, measured in

ms

ms

. More CPU-heavy things will increase it (for example, hashing passwords). This is not the same as the time a

fetch

fetch

request takes.
Wall Time: the actual amount of time a Worker runs for, as though you measured it with a clock or your browser DevTools

Ssamsung Okay, I tested it, it stays longer than 30 seconds. a 2-minute connection was pr...

fry69•11/9/24, 8:23 PM

Unless you have an endless for loop running in your worker to eat CPU time, you might have just measured real (wall) time, which does not matter. Workers can run for a year I think if they do not consume CPU, see -> https://developers.cloudflare.com/workers/platform/limits/#duration

Isaac McFadyen•11/9/24, 8:23 PM

You get 30 seconds of cpu time, so that means that if your WebSocket isn't doing much it could theoretically last for many minutes, although it's not a 100% because sometimes websockets are killed by Cloudflare for internal reasons.

samsung•11/9/24, 8:27 PM

"wall time" is not included in the fee ?

samsung•11/9/24, 8:28 PM

and execution duration ?

Ssamsung "wall time" is not included in the fee ?

fry69•11/9/24, 8:28 PM

Correct. Wall time does not matter, only CPU time.
For billing only CPU and number of Worker requests matter (not subrequests).

samsung•11/9/24, 8:49 PM

there is no pricing based on durable object logic, is there?

samsung•11/9/24, 8:50 PM

is there any link explaining?

Ssamsung is there any link explaining?

fry69•11/9/24, 8:50 PM

See here -> https://developers.cloudflare.com/durable-objects/platform/pricing/

samsung•11/9/24, 8:57 PM

I'm confused about this.

samsung•11/9/24, 8:58 PM

Can this method be similar to the durable object pricing?

samsung•11/9/24, 8:59 PM

because 1 request fee is 1 hour connection and more

samsung•11/9/24, 9:04 PM

am I wrong?

1984 Ford Laser•11/9/24, 10:27 PM

I kinda assumed that WebSockets on Workers would just get charged at the same rate as WebSockets on DOs, by GB-sec

user•11/10/24, 1:20 AM

wasnt sure where to post this so i assume this is where, but, is it possible to entirely limit access to a cloudflared tunnel to a worker?

user•11/10/24, 1:20 AM

i couldnt find a zero trust channel but i also have terrible eyesight

user•11/10/24, 1:28 AM

nevermind i just made a WAF for it

Yash Bindal (yB)•11/10/24, 6:04 AM

what's the best way to do this with reverse proxy

I want to take url /academy?id=25
show content of this page on
/academy/academy-name

25 will change to name using json

0x146231489231923•11/10/24, 9:32 AM

https://developers.cloudflare.com/workers/examples/multiple-cron-triggers/#test-cron-triggers-using-wrangler

Cloudflare Docs

Multiple Cron Triggers | Cloudflare Workers docs

Set multiple Cron Triggers on three different schedules.