Custom Hostnames (CF for SaaS) - some domains 522
Hi All,
We have custom hostnames enabled for a zone (docs.page), and have added a number of custom hostnames to test.
All hostnames are verified (green certificate status + hostname status). These hostnames are supposed to connect to a cloudflare worker, which is routed via the DNS record (this is setup).
The problem:
Some of these hostnames work (they hit the worker as expected), and some of them don't. Those that don't, have a 522 error, and there are no logs on the worker - it looks like an CF internal issue.
We've used a bunch of domains (both within cloudflare dns and outside):
Broken:
- https://test-docs.tangents.tech/ (Namecheap DNS)
- https://test.docs.page/ (Clouldflare DNS, same zone)
+ https://docs-test.giteye.io/ (Cloudflare DNS, same account)
Working:
- https://docs-test.elliothesp.co.uk/ (Cloudflare DNS, different account) - https://test-docs.unverified.lol/ (Cloudflare DNS, different account) We're totally stumped as to why this is happening - how do we go about debugging and resolving? Looks like those in the same account/zone are broken, but this shouldn't be the case...?
- https://docs-test.elliothesp.co.uk/ (Cloudflare DNS, different account) - https://test-docs.unverified.lol/ (Cloudflare DNS, different account) We're totally stumped as to why this is happening - how do we go about debugging and resolving? Looks like those in the same account/zone are broken, but this shouldn't be the case...?
3 Replies
You just have a wildcard worker route catching all? If you Account level -> trace one of those broken URLs, what do you see?
