Worker routing refuse to work for one domain
I have worker setup with two routes to two domains.
But one of the domains refuse to route, no matter what I do, the request goes straight to the DNS address, without being routed to the worker.
I tried:
Uproxying and proxying again all relates A records.
Delete all other routes but the non-working one.
Routing /test* only to each domain.
I’ve compared all of the dashboard settings of the domains and I don’t see anything that is different.
What do I miss? Why is one domain not routing to the worker?
9 Replies
What's the setup for the non-working domain? Is it pointing at a Cf for SSL partner like shopify?
it has a few A records to Bubble
I was hoping to catch a ceratin path before it goes to Bubble. I got it working with another domain as a test and now, this one just won't route any request
Looks like Bubble is a SSL for SaaS partner, so you're probably hitting the o2o (orange to orange aka cf to cf) limitation
https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/
Basically, because you're already going through Cloudflare, and Bubble is an SSL for SaaS partner, it skips through your cloudflare website/zone settings for a few items like Workers and uses Bubble's instead.
If you're Enterprise, you can get what is called "o2o" enabled so it goes through your cloudflare website/zone settings first. If you're not an Enterprise customer, you could try asking: https://community.cloudflare.com/t/status-of-shopify-o2o-for-non-enterprise-cloudflare-users/382415/14?u=chaika
Thank you, that explains it
Is there any technical way to bypass this? maybe using Page Rules or any other method?
Nothing like that will apply as long as you are pointed to Bubble without o2o enabled
Thanks
Will that still be the case if I put Bubble on a subdomain ?
For example, is it possible for example.com to be routed to workers and only app.example.com points to Bubble?
it should be per hostname yea
I would just make sure to delete it on Bubble's side as well, CF has made some fixes which should properly remove the hold on your hostname if you remove/change the dns record, but it used to be that even if you changed the DNS Record to anything else while proxied, the connection would still exist to Bubble and traffic would continue to flow to them, until they deleted the custom hostname on their end
Is my understanding of this issue correct? It sounds like using Cloudflare features for sites already on Cloudflare (like Bubble) is more difficult and requires a higher plan than sites not on Cloudflare. That seems counterintuitive to me, so I'm double checking.
There's an old version of SSL for SaaS/Cf for SaaS which some Enterprise's use which simply ignores your zone's(website in Cloudflare) settings and uses their zones settings instead. I believe the reason was technical, wanting to avoid going through the entire flow twice for your zone + theirs, or something else. If you need o2o enabled so your settings apply, and you don't have Enterprise, try that email in the thread linked above and they'll enable it. Modern CF for SaaS/the version most customers use should just work with your zone's settings.