I am experiencing incidents when I try to access my domains. I always get the error 522, I have investigated and followed the steps to solve it but it seems that the error is in cloudflare side, I have seen that there is an open incidence (incidents/7j0gb2ws3df3)
on the other hand I have tried to migrate a static page to cloudflare and after modifying the DNS to point to the cloudflare domain, I am also getting the error 522
can we be sure that this is a cloudflare issue or can it be another cause?
The only error code I’ve seen reported out of that incident was 502s, which are now seem to be super rare, and at least personally haven’t triggered my monitoring in 2 days.
Are you talking about Cloudflare Pages? If so, make sure you add the domain via the Custom Domain tab: [Custom domains · Cloudflare Pages docs]
And I already update the CNAME previously, and i´m retrieving always the 522 error code
the domains are pointing to a server, and after verifying the steps of that url, the server load … even restarting server and services… still having the problem, so I tried migrating a static page to cloudflare itself and after updating the DNS and pointing to it, I still get the same type of error, so I understand that probably the error is on the side of cloudflare…
Can you clarify what you mean by “migrating the static page to Cloudflare itself”? Are you talking about with Cloudflare Pages? Cloudflare Workers? Worker Sites?
Otherwise, an easy thing to test is disabling cloudflare proxy, or outright pausing cloudflare on your entire site (Pause Cloudflare · Cloudflare Fundamentals docs), and seeing if the issue persists. If, after pausing it, once no longer get a cloudflare error page, if you instead a browser error, then it’s on your origin’s end, not Cloudflare’s.
Also, if your SSL/TLS mode is set to Full or Full (Strict) (Recommended), Cloudflare attempt to connect over https /port 443, if you connect over https / port 443. If your origin doesn’t support https / port 443, that would be one reason for the error. In contrast, if you are on Flexible or Off and your origin does not support http / port 80, but does https / port 443, then you should switch it to Full (Strict).
Indeed, I was talking about cloudflare pages, deploying a repository as page, the internal cloudflare page works properly, but the subdomain added in CNAME is answering status code 522 as well, and it is fully stored in cloudflare
anyway I will check your tips about pause cloudflare thanks! But this should not affect to the cloudflare page
Thanks for clarifying.
You can’t just create the CNAME to the pages project, that’s not enough to make it work. You need to add the Custom Domain within the Pages Project Custom Domains tab: Custom domains · Cloudflare Pages docs
Otherwise, you’ll get a 522, but for a different reason then when your origin wasn’t working. Probably a bit confusing, I would understand.
Wow, really? that’s funny!
I did it manually at the begining… and after your comment I followed the steps from the page, but in the end the result in step 2, DNS configuration, was to replace the CNAME previously added by the same one, and I aborted the change.
I have done it again, and you are right, by doing it from the page if the DNS works.
so I imagine that in the end it is not a cloudflare problem and something will happen on the server side.
By the way, the other issue was solved, it was related to one of my routers
the confusion came when receiving the same status code as when displaying a cloudflare page by changing only the DNS without publishing the change from the cloudflare page