can't make route matching work with wildcard subdomain
I just created the worker with the starter proxy template and added my route (*.app.jeto.ai) and it don't work, am I doing something wrong? Should I create something on the zone?
5 Replies
Yep, you need corresponding DNS Records for any routes, and you need an SSL Certificate as well if it's deeper then 1 level/not covered by the universal
Create a DNS Record
AAAA *.app.jeto.ai 100:: Proxied 100:: is IPv6 Discard, used for originless records, basically a "Hey Cloudflare, proxy these records through your request flow, something will handle it before it tries to connect to the non-existent origin
Then you would need to create an ACM Certificate as well, or if you have Total TLS on, I believe it would do it for you
That is, if you don't already have records created for those subdomains and your intent is to have the worker run in front of them, if so, then those records should stay. I'm not sure which starter prroxy template you usedI already created this record
but I have an error telling that the record does not have a certificate
probably the TLS thing you mentioned
how can I configure that?
ahh ok, yea that's the second part I mentioned. The default Universal you get only covers first level subdomains. You'd need to subscribe to Advanced Certificate Manager (ACM) ($10 usd/month) to get a wildcard cert for
*.app.jeto.ai
If you don't want to buy ACM, your options are basically to run first level (i.e *.jeto.ai), or buy a separate domain like appjeto.ai, and have it wildcard on the first level of that (*.appjeto.ai)I see
great! thank you very much
I will try buy the ACM
Sure, once you do that, you can order an adv. cert (you get 100 included with the subscription), and just specify the hostname
*.app.jeto.ai and whatever cert authority/length you want (CF will handle deploying/renewing/etc, it's just create and forget)