When you receive a 522 Error on a website, it is the server side error and Cloudflare is not to be blamed. It means Cloudflare is not able to establish a connection with the web servers. If the servers don’t respond to the queries within 60 seconds, the connection gets timed out and the website flaunts Error 522.
So they asked me to open a ticket and they would look further into it.
False. About 10% of the internet’s traffic goes through Cloudflare.
Typically this error comes up because of a firewall setting blocking Cloudflare. In some cases the firewall sees the same IP (Cloudflare’s) too much, and further connections are blocked. The fix is to allowlist Cloudflare’s IP at the host/firewall.
Okay, my host told me that they have whitelisted all Cloudflare’s IP addresses.
But it keeps showing 522.
I’ve checked the error in Google search console, the robot txt to the error 522 url is allowed.
Did you mark those URLs as fixed in Google’s Console? If not, you should do so. Then wait a while (maybe a week?) to see if the error returns. For an immediate test - and indexing request - you can use their Crawl > Fetch as Google utility.
