Hi, question regarding pricing and plans. If i purchased WFP on my account, do i still need to purch

Hi, question regarding pricing and plans.
If i purchased WFP on my account, do i still need to purchase Workers Paid for anything? Also, how does my domain plan comes into to play here? will the plan (free / pro / business) of the domain i attached to my dispatch worker affect it?

Thanks.

OOle Melhus Can we upload source maps with the wfp user script?

Walshy•6/21/24, 1:40 PM

you should be able to yes

DDORSHT Hi, question regarding pricing and plans. If i purchased WFP on my account, do i...

Walshy•6/21/24, 1:43 PM

You probably don't need it but I'd recommend having it
as for the zone plan, doesn't play a factor in Workers

Erisa•6/22/24, 8:09 AM

If you're on a startup plan then contact support, it likely needs manually enabling

Rahul Raikwar•6/25/24, 1:32 PM

"Cloudflare webhook is being called multiple times, and builds are being created repeatedly. Is there any way to stop this?"

RRahul Raikwar "Cloudflare webhook is being called multiple times, and builds are being created...

Hard@Work•6/25/24, 1:41 PM

?channel-crossposting

Flare•6/25/24, 1:41 PM

Please do not post your question in multiple channels per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

rob•7/2/24, 7:15 PM

so like: scriptName.org.website.com/* would trigger the dispatch worker ? Im trying to add a route in workers route

rob•7/2/24, 8:00 PM

what else do i need to do besides adding the route to the dispatch worker? bc i added

*.domain.com/*

*.domain.com/*

i get

DNS_PROBE_FINISHED_NXDOMAIN -- What do i need to set it to on DNS management for the doamin on cloudflare * and point it to 192.0.0.2 . Proxied?

DarkDeviL•7/2/24, 8:10 PM

AAAA

AAAA

towards

100::

100::

, Proxied ( :cloudflare: ).

rob•7/2/24, 8:12 PM

so * 100:: proxied

rob•7/2/24, 8:19 PM

hm.. ERR_SSL_VERSION_OR_CIPHER_MISMATCH

rob•7/2/24, 9:33 PM

Any ideas, on the cipher mismatch -prob because the CF cert doesnt cover double subdomains right? I need an advanced cert for that or my own external off of cf ?

Rrob Any ideas, on the cipher mismatch -prob because the CF cert doesnt cover double ...

Erisa•7/2/24, 9:47 PM

Your answer to your own question is correct - the cipher mismatch error means there's no matching edge certificate on Cloudflare, for second-level subdomains this is because the default Universal SSL does not support them. The fix is to issue an advanced certificate (requires purchasing ACM for $10/mo) or upload your own certificate (requires a Business plan, $250/mo)

Please note if you plan to make use of double level wildcards in your application e.g.

*.*.domain.com

*.*.domain.com

, this is not possible for a single SSL/TLS certificate due to inherent TLS protocol restrictions. You will need to issue a new certificate (or hostname for existing certificate) for each first level wildcard e.g.

*.org1.domain.com

*.org1.domain.com

*.org2.domain.com

*.org2.domain.com

and so on.

rob•7/2/24, 9:48 PM

Oh i see! so if i wanred to do scriptName.userName.mydoamin.com thats a no go on double wildcard, i'd have to actually buy a cert for each "userName" correct? -- i couldnt just buy the $10 advanced and cover it

rob•7/2/24, 9:49 PM

OR let customers point their domain and then its just a sub domain for their domain for each diff worker/script

rob•7/2/24, 9:49 PM

hmph.

Erisa•7/2/24, 9:51 PM

You can't issue a certificate with two wildcards so you'd have to explicitly include the username in each certificate. You'd likely run against limits pretty fast doing that

rob•7/2/24, 9:51 PM

yea or bring my own external ones and roll my own code there.. more overhead lol

Erisa•7/2/24, 9:51 PM

Similar services will do

scriptname-username.example.com

scriptname-username.example.com

to bypass this

rob•7/2/24, 9:52 PM

yep seems like the way to go, was gonna be my next route , no pun intended ; )

Erisa•7/2/24, 9:53 PM

Yeah that's your most realistic option, the path of double wildcard is imo not worth the added struggle

Erisa•7/2/24, 9:53 PM

I mean that is what Cloudflare does for workers but.. they can issue certificates without limits aha

rob•7/2/24, 9:53 PM

yah i'll reserve that right for the big orange cloud themselves

rob•7/2/24, 9:53 PM

yea the big guy upstairs can handle all that

rob•7/2/24, 9:55 PM

welp thanks for the help appreciate it

Nick Randall•7/4/24, 2:38 AM

Is it possible to use CRON triggers with workers for platforms?

NNick Randall Is it possible to use CRON triggers with workers for platforms?

jman•7/4/24, 2:33 PM

I don’t believe so, directly, since I don’t see the CRON config available on the api docs for WFP

https://developers.cloudflare.com/api/

But one alternative would be to trigger with durable object alarms

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

winnepeach•7/6/24, 5:03 AM

Can I call multiple user workers from a dynamic dispatch worker in a single request? And if so, how would that be billed?

rob•7/6/24, 11:44 PM

Simultaneously ?

Rrob Simultaneously ?

Lume•7/7/24, 1:55 PM

In the same request to the dispatch worker.

Lume•7/7/24, 3:52 PM

export default {
    async fetch(request, env) {
        try {
            
            let workerName1 = "worker1";
            let userWorker1 = env.dispatcher.get(workerName1);
            let result1 =  await userWorker1.fetch(request);

            let workerName2 = "worker2";
            let userWorker2 = env.dispatcher.get(workerName2);
            let result2 =  await userWorker2.fetch(request);
        } catch (e) {
            if (e.message.startsWith('Worker not found')) {
    
                return new Response('', { status: 404 });
            }
            return new Response(e.message, { status: 500 });
        }
    },
};

export default {
    async fetch(request, env) {
        try {
            
            let workerName1 = "worker1";
            let userWorker1 = env.dispatcher.get(workerName1);
            let result1 =  await userWorker1.fetch(request);

            let workerName2 = "worker2";
            let userWorker2 = env.dispatcher.get(workerName2);
            let result2 =  await userWorker2.fetch(request);
        } catch (e) {
            if (e.message.startsWith('Worker not found')) {
    
                return new Response('', { status: 404 });
            }
            return new Response(e.message, { status: 500 });
        }
    },
};

Can I do something like this, and how is this billed?

rob•7/7/24, 8:35 PM

try waitUntil also , if you dont want to wait for the first one to finish

Rrob try waitUntil also , if you dont want to wait for the first one to finish

Lume•7/8/24, 11:00 AM

Ok, but how will my example be billed? 2 requests or 1 request?

Walshy•7/8/24, 11:05 AM

Each user Worker request is billed

WWalshy Each user Worker request is billed

Lume•7/8/24, 3:43 PM

Thank you. If I don't call a user worker due to an error I won't be billed, right?

LLume Thank you. If I don't call a user worker due to an error I won't be billed, righ...

Hard@Work•7/9/24, 8:48 AM

You will be billed for the Dispatch Worker invocation, but not for any user Worker invocations

HHard@Work You will be billed for the Dispatch Worker invocation, but not for any user Work...

Lume•7/9/24, 11:05 AM

So in the above example I will be billed 3 times?? 1 Dispatch Worker invocation, 2 User Worker invocation

Ace•7/9/24, 11:09 AM

Hi, I have a question related to workers for platforms. is there a way to limit the max total usage of a user worker.
the usecase is as follows -

the user will deploy their own workers (+ durable objects).
our dispatch namespace will call the user worker.

however we'd want to avoid or block user-workers & durable objects if they exceed their usage tier limits (say 1million gb/s) . We'd like to ideally stop the workers & durable objects for that user (please note - we want to stop, and not permanently delete.)

ideally we'd wish there exists an api from which we can set & increase the limits. but in case that is not available.

how do we track individual usage per user worker script
how do we stop/block that worker, and later unblock it

from my understanding we'd have to do the blocking ourselves in the dispatch namespace. and maybe poll the usage analytics per user worker script from cloudflare api.

what would be the best way to achieve the above usecase. thankx for the help

ottermanempire•7/9/24, 3:38 PM

Hi, I'm using the Cloudflare for SaaS setup with workers. We added custom domains to SSL/TLS section -> Custom Hostnames section via the API a couple months ago. I'm noticing that one of our client domains has expired, do the domains not automatically renew? Will we need our clients to add new validation records every few months?

Oottermanempire Hi, I'm using the Cloudflare for SaaS setup with workers. We added custom domain...

DaniFoldi•7/9/24, 4:44 PM

You can use (and I'd recommend) HTTP validation, which only needs the CNAME record to be in place. DNS validation, while recommended in the UI for some reason, needs manual intervention every time the cert has to be renewed, like you said

Ace•7/10/24, 2:42 PM

do workers for platforms not show logs for durable objects? it is working in a normal worker/durable object. but for workers deployed to a dispatch namespace I can only see the logs produced by the dispatch worker & user-worker. but not the durable object. for both tail & logpush (worker trace events).

Ace•7/10/24, 7:17 PM

maybe relevant for this thread as well wrangler

HHard@Work You will be billed for the Dispatch Worker invocation, but not for any user Work...

Lume•7/13/24, 4:43 PM

Will I be billed 1 time or 3 times? 1 Dispatch Worker invocation, 2 User Worker invocation

ottermanempire•7/18/24, 1:42 PM

We had a client add the _acme-challenge and _cf-custom-hostname txt records as well as the cname records to their dns. However, cloudflare hasn't picked up the _acme-challenge record at all over the past week or so. Just walked them through and got them some new records since the 7 days until expiration was coming up. Is there a reason cloudflare might not be picking up the txt record? The client was using namecheap for their dns if that matters. (Edit: the new txt record isn't getting picked up either, confirmed on the call that it was set up correctly).

export default { async fetch(request, env) { try { let workerName1 = "worker1"; let userWorker1 = env.dispatcher.get(workerName1); let result1 = await userWorker1.fetch(request); let workerName2 = "worker2"; let userWorker2 = env.dispatcher.get(workerName2); let result2 = await userWorker2.fetch(request); } catch (e) { if (e.message.startsWith('Worker not found')) { return new Response('', { status: 404 }); } return new Response(e.message, { status: 500 }); } }, };

Hi, question regarding pricing and plans. If i purchased WFP on my account, do i still need to purch

Similar Threads

Similar Threads

Similar Threads