HDNS updates can take up to 24 hours
SThanks @HardlyHolidayin’
SI got this
HCan you screenshot the entire redirect rule?
HTry making the
NEET lowercaseSIts working now
SThank you 
R@Erisa | Support Engineer I am extremely sorry for asking this again and again, but is the image merge happend? Its just one of my clients driving me nuts and it is 16 in every timezones out there
EI do not believe so, but I don't have any further insight to share
EHi, could anyone explain me in simple terms (I would have put ELIF), why I am getting this error in one worker:
Ri keep getting error code: 1042? i guess you cant fetch from one worker to another on the same account? how do i get around this?
Rsomething to do with binding service workers
Rso i named my service binding getData...
is this how i call service worker 2 from service worker 1 ?
env.getData.fetch(url to service worker 2)
is this how i call service worker 2 from service worker 1 ?
env.getData.fetch(url to service worker 2)
Rweird still not working
Rwhy am i even using 2? i'll just throw them all together and call it day lol
Eanyone using workers trace events with logpush? my log jobs configuration page is throwing a 404 error page - It seems that I don’t have access, I’m on workers paid plan
CI have. I believe if you signed up a long time ago/are on an old paid plan, you need to go to Workers & Pages -> Default Usage Model -> Change and it should ask you to agree to changing your plan to the latest one.
If you're Enterprise, CSM
If you're Enterprise, CSM
EAlready done that, I still have many workers on the old bundled but my default plan is the new Standard, I'm not enterprise
Cyea the issue isn't the usage model, but that there's actual old Workers Paid Plans that you could be subscribed to. If you don't get the popup on that/can use Standard I don't think that could be the case
You're looking at the account one, right? Magic Link: https://dash.cloudflare.com/?to=/:account/logs
You're looking at the account one, right? Magic Link: https://dash.cloudflare.com/?to=/:account/logs
Eand you are right, just checked another account I have with cloudflare and there is it, the Logs menu, the question is, should I try to disable and enable workers paid plan?
Ethe account I'm having trouble is showing "404 | We can't find the page you're looking for." on that page, the new account is showing the correct page, surely I'm a very early adopter of the workers paid plan on this account with problems
CInteresting, yea if you signed up to Paid Workers early could def be that older plan issue. I think you might just have to ticket, not sure if it would be either Billing or Account
Eand I tried to de-activate and activate the workers paid plan only to be welcomed with a we don't support re-enabling it until the billing cycle ends 
CYeah at this point I feel account ticket is probably the best way
Ethis was the response:
Hi there,
Thank you for contacting Cloudflare Support, we are sorry that you are experiencing some difficulties.
Unfortunately, as of right now, a cancelled subscription cannot be re-instated. Once your current subscription has completed cancelled , then you can set up a new subscription.
We apologize for the inconveniences,
Hi there,
Thank you for contacting Cloudflare Support, we are sorry that you are experiencing some difficulties.
Unfortunately, as of right now, a cancelled subscription cannot be re-instated. Once your current subscription has completed cancelled , then you can set up a new subscription.
We apologize for the inconveniences,
CFor which issue? The subscription issue or unable to create logpush jobs one?
Ere-enable workers paid plan, the other issue is still pending on the account tickets section
Eprobably they are still dealing with issues from the last downtime.. but I'm worried about this client spending almost 1000$ monthly and still getting problems with support
Mwas looking to enable web analytics but i enabled Analytics Engine too, how do i turn it off ? or let it be ?
BHi all, I had a question around the service bindings. One thing that is very convenient is that you can easily bind any cloudflare service into your workers (database, r2, kv, etc) without having to deal with credentials and connection details.
So I was hoping that service-to-service bindings would work in a similar fashion, namely that I could just
I am probably missing some context here, and maybe there is a technical implication that makes this non-trivial to implement, but imo would be very convenient DX if you can just call directly into another service without needing additional configuration.
So I was hoping that service-to-service bindings would work in a similar fashion, namely that I could just
ctx.otherService.fetch("/some/relative/path") that would call that service through an internal network. However, that seems not to be the case, I now have to bind the service, but also somehow configure the url of how to access that service.I am probably missing some context here, and maybe there is a technical implication that makes this non-trivial to implement, but imo would be very convenient DX if you can just call directly into another service without needing additional configuration.
Bor am I misunderstanding how service bindings are supposed to be used?
EYou can use service to service as
const authResponse = await env.auth.fetch(request.clone());Bboth services then need to have the same route?
AYou create your own request, and you can use any URL you like.
AYou can hit the binded worker with example.com/whatever if you want
Bany url? I tried with a relative one and that didn't work
AIt needs a host
ABut it can be any host
Bthat is good to know, I understand that the binding is identical to
Fetcher that a worker implements, but it is a bit confusing that you must pass a host, while in fact it is not used at all...
KProbably for the best so
new URL(req.url) doesn't break in Service Bindings/Durable ObjectsBanyway thanks for clarifying guys : )
Bone last thing to double check, let's say worker A has a service binding to worker B, and worker B shoud not be accesible from the outside world, I can simply remove all routes of worker B and only communicate with this worker through the service binding of worker A, right?
ECorrect
BGreat, thanks again everyone
AYou can set workers_dev = false in wrangler.toml too, just so there’s no URLs generated for it even in dev
BGood tip, thanks
JDoes cloudflare have a table displaying what features do and dont work within: Zone, workers.dev, miniflare/local?
ZNot that I know of
