Disabling IPV6 is still an option while its disabled in the UI? Nice to know 😅
Disabling IPV6 is still an option while its disabled in the UI? Nice to know 
Doh, so the certificate handling is different, but the TLS/cert perf is the same?
KYes its the limitation that the upstream service needs an IPV4 because it still does not support IPV6
KAnd it needs to be a valid IPv4 because otherwise there will be connection issues between the client and the service
Cvia the api yea
CYou can always delete it
Cit's just an adv. cert under Edge Certs
Cif you're fast enough or script it, you can delete it before it issues
Dso when I do curl -v, I see only the SSL cert for the domain and not the wildcard ;P
Cyea Worker Custom Domains are just really hacky. You don't need ACM to delete them, or use it. They do count against your ACM Quota though, and show up there
USpeaking of ACM I think the workers custom domains does use your limit of ACM if you have it or it least did in the past 
Kthe main feature of custom domains (imo) is not having same-zone fetch issues, but that has been broken since day 1
K
UI just like how it shows in the dns thats why I use it 
Uservice bindings are better for fetching anyways so that feature is useless imo
Cfor me custom domains are just easier and I can just snipe the adv. cert
Cno reason to use routes over custom domains if you intend to use the entire subdomain, routes are messier, configuration slightly hidden, and can be misconfigured
Udocs also say this so I just follow it
Dwe have Total TLS on and our cert count is 0 out of 100.
Dand we have 81 certs
INow that we have descriptions on DNS records I just add a description to the Worker record and use routes 
KIt did indeed work. Thanks for the hint!
KNot the best solution but the only possible right now. But having it disabled for the whole zone... suboptimal
Ctotal tls certs don't count
Cconvince your upstream to move on from 2006 and support ipv6 
Dahhh
KThey haven't updated their software in the last 4 years but we sadly have to integrate it into our app
KI wish they would do it, but I doubt it
Disn't that ent-only? or am I thinking about tags?
CNeither are Ent-only
CComments are on free, Tags are Pro or higher
Dooo nice! thanks
JHi CF developers. I have an existing worker, and I cannot figure out how to have a 'staging' version and a 'production' version of the same worker. I have tried running
npx wrangler deploy --env production and npx wrangler deploy --env staging but all it does it create a new worker with -production or -staging at the end.JCan someone point me in the right direction?
Cbut all it does it create a new worker with -production or -staging at the end.That is how environments work right now with Wrangler
JI have other workers that in the dashboard are named the same, and they have a dropdown on the worker page where I can select environment
CThere is bits and pieces in the dashboard about the old Service Environments system if you're being confused by that, that shows production and such. James has a write up explaining that all here: https://community.cloudflare.com/t/environments-vs-deployments/451036/2?u=chaika
CThe TLDR being the Wrangler way with entirely different Workers is the best way right now and the intended way. You can have specific settings in your wrangler.toml for specific environments as well https://developers.cloudflare.com/workers/wrangler/environments/
Deploy the same Worker application with different configuration for each environment.
JSo that functionality has been removed? (having the same worker have multiple environments).
CEssentially, iirc it never fully worked anyway
Cthere's just bits of pieces of it left over
UI dont even think it existed for more than a month tbh
JI have clients that have that functionality currently in their dashboard working.. but ok, thanks for the information!
JI appreciate you taking the time
CI think if they created them before they didn't get taken away, but I imagine the functionality is still half baked/broken/etc
CI don't have any to test with though
FWhat is the best way to debug a 1101 Error and tail says Error: The script will never return a response. For context we are hosting an astro site with SSR as a "sandbox" environment for customers to test CMS changes before deploying (the final page is static). But for some "some minutes - minutes could also last for 20-25 minutes" the page works perfeclty fine and then for a long time there is the 1101 Error and I really cant find a way to debug, etc. Any help / direction would be really appreciated.
AHello
Is anyone using OpenTelemetry in workers (for prometheus format)?
I find it really confusing to just expose some prometheus metrics: MeterProvider, views, MetricReader, etc all the naming and docs are confusing
Is anyone using OpenTelemetry in workers (for prometheus format)?
@opentelemetry/api, @opentelemetry/sdk-metrics, @opentelemetry/exporter-prometheus and co?I find it really confusing to just expose some prometheus metrics: MeterProvider, views, MetricReader, etc all the naming and docs are confusing
KThe Workers ran by DevProd (the team behind Wrangler) use promjs
KAyou mean this one? https://github.com/weaveworks/promjs it is deprecated
https://github.com/siimon/prom-client was so much simpler, but I wanted to give a try to otel to do kind of the same
https://github.com/siimon/prom-client was so much simpler, but I wanted to give a try to otel to do kind of the same
