Hello. We have a self-managed bare metal server through OVH. Once before, we received
522 errors through Cloudflare in San Jose, CA and Los Angeles, CA, and the same problem happened once again.
Turning off Cloudflare resolves these problems for clients near these locations.
I made a ticket with OVH and they denied they had blocked Cloudflare IP ranges and stated they do not block any Cloudflare IPs. Our firewall through OVH is turned off.
Again, our server is self-managed, and we did not have a software firewall on, fail2ban, or anything that can block IPs. I can confirm that nothing was inadvertently blocked on UFW/iptables.
Can Cloudflare please investigate these
I should also add that these
522 errors were intermittent and unpredictable until Cloudflare is turned off, which means IPs probably weren’t actually blocked. And sometimes certain resources would load, but not others. It also leads me to believe this is a very intermittent (but not widespread) problem on Cloudflare’s end.
Which of the
522 quickfix ideas have you tried so far?
Try the suggestions in this Community Tip to help you fix Error
522 “ERR CONNECTION TIMED OUT” in Google Chrome or “The connection has timed out” in Firefox.
A 522 error happens when a TCP connection to the web server could not be established. This typically happens when Cloudflare requests to the origin (your webserver) get blocked. When this happens, you’ll see “ERR_CONNECTION_TIMED_OUT”.
Quick Fix Ideas
Make sure that you’re not blocking Cloudflare IPs in .hta…
cf does not generate
522, we simply pass them from the origin
Thanks. What you said about CF not generating
522 errors makes a lot of sense.
I’m reaching back out to my host as it seemed like their investigation was rather lazy.
I’ve basically tried all of those quickfix ideas and then some. I’m nearly certain it’s not our server causing the issue.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.