Cloudflare Pages + Custom Hostnames setup
Domain: www.camit.cl
Error: HTTP/2 522 (Ray IDs e.g. 99f8ddaffb79cad4)
Pages project: custom-origin.munityos.com (Worker site-worker)
Summary:
This hostname is part of our Cloudflare for SaaS/Pages setup. Other custom hostnames pointing to the same worker (www.agendapanda.com, www.targeterapp.com, www.dialogcreator.com)
work fine.
Only www.camit.cl fails. When we curl your fallback origin directly with the camit host header we get HTTP/2 403:
curl -I https://custom-origin.munityos.com/ --header "Host: www.camit.cl"
→ HTTP/2 403
That means the request never reaches our worker (the Pages log stream shows no entries for this hostname).
Steps already taken:
1. Re-added the custom hostname via the dashboard; CNAME is proxied to custom-origin.munityos.com, SSL status Active.
2. Verified dig +short www.camit.cl returns Cloudflare IPs and the custom hostname status is Active.
3. Deployed logging inside the worker; logs appear for other hostnames but not for www.camit.cl.
4. Backend APIs resolve the workspace (/workspaces/by-domain/www.camit.cl).
5. Running the origin curl above is the only case returning 403.
Request:
Could you investigate why the custom hostname www.camit.cl still returns 403/522 while the same setup works for other domains? Is there additional configuration needed for this
hostname so the origin accepts Host: www.camit.cl?
Error: HTTP/2 522 (Ray IDs e.g. 99f8ddaffb79cad4)
Pages project: custom-origin.munityos.com (Worker site-worker)
Summary:
This hostname is part of our Cloudflare for SaaS/Pages setup. Other custom hostnames pointing to the same worker (www.agendapanda.com, www.targeterapp.com, www.dialogcreator.com)
work fine.
Only www.camit.cl fails. When we curl your fallback origin directly with the camit host header we get HTTP/2 403:
curl -I https://custom-origin.munityos.com/ --header "Host: www.camit.cl"
→ HTTP/2 403
That means the request never reaches our worker (the Pages log stream shows no entries for this hostname).
Steps already taken:
1. Re-added the custom hostname via the dashboard; CNAME is proxied to custom-origin.munityos.com, SSL status Active.
2. Verified dig +short www.camit.cl returns Cloudflare IPs and the custom hostname status is Active.
3. Deployed logging inside the worker; logs appear for other hostnames but not for www.camit.cl.
4. Backend APIs resolve the workspace (/workspaces/by-domain/www.camit.cl).
5. Running the origin curl above is the only case returning 403.
Request:
Could you investigate why the custom hostname www.camit.cl still returns 403/522 while the same setup works for other domains? Is there additional configuration needed for this
hostname so the origin accepts Host: www.camit.cl?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
