Hi, I’m trying to follow this guide in order to set up custom hostnames with a CF Worker:
I’m running into the exact same problem as this issue I found on the forums in the past:
It seems like this was a bug that was fixed by the Cloudflare team in the past but I have the same setup as that person and I’m getting the same 522 error.
workerName.workers.devworker with a worker route of
proxy.mywebsite.com/*pointing to the worker.
- I have
proxy.mywebsite.comset up as a fallback origin in Custom Hostnames.
- I have a
proxywith a content of
mywebsite.com, like the Cloudflare document above describes
- I set up a Cloudflare Custom Hostname for
customerwebsite.com. The certificate status and hostname status is Active.
- On the customer DNS side, I have a
wwwwith a value of
curl -I https://www.customerwebsite.com/ returns a
curl -I https://proxy.mywebsite.com/ returns a
200 and I see the request in Cloudflare
Does Cloudflare still support using a worker as the fallback origin for custom hostnames? Does this not work when trying to serve custom hostnames from ONLY
proxy.mywebsite.com? I have other endpoints like
app.mywebsite.com that I do not want to serve custom hostnames from. Do I need to use a different domain to serve custom hostnames from? For example,
proxy.mywebsite.cloud instead of