I'm confused a bit, is "cloudflare for
I'm confused a bit, is "cloudflare for saas" a feature of "workers for platforms"? I'm trying to setup (the third time 😅) custom hostnames so that customers can point their domain to my worker. But I can't get this to work. The fallback origin is a worker, I've setup the
AAAA 100::, origin seems fine, hostname added, validation completed – but when I access the customer domain (that should be now pointing to my fallback origin (worker)), I always get a cf page with 522.
So do I need an activate "Workers for Platforms" (meaning do I have to upgrade my page plan in order to enable it?)7 Replies
@dsds10 unrelated. You don't need to activate it. The error you are hitting is probably because you didn't add a wildcard route, https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin/
Worker Routes see the custom hostname (yourcustomer.com) as the incoming url, thus you need a wildcard route
@Chaika ahh now I understand, wasn't aware that Worker Routes see the actual url. That makes sense, but only the
*/* variant works, the other one suggests to set Worker: None – how is CF then supposed to know where to route to? It says "only routes custom hostname traffic to the Worker", but what Worker? It is set to "none", and the fallback origin is using 100::The most specific route matches, so the idea of that is to wildcard catch customer domains and then use a more specific one to exclude your own domain (assuming you don't want all hostnames on your domain to go to that worker)
Makes sense, thank you for the clarification 😉
@Chaika one last thing: Is there anyway to offer customers to route their main domain to my service? They might require to set an
A record. As of https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/ I would need to contact CF in order to obtain IPs. Is this an enterprise feature?Cloudflare Docs
Apex proxying · Cloudflare for Platforms docs
Apex proxying allows your customers to use their apex domains (example.com) with your SaaS application.
Apex proxying by assigning you IPs is Enterprise yeah. Otherwise for pay as you go saas if their DNS provider supports cname on root (cloudflare does), sometimes shown as alias/aname records they can use that. Although if the DNS provider is non-cloudflare and using apex, they need to add the prevalidation txt first, wait for verify and then record last I knew
got it, thank you! 🙂