Thank you definitely appreciate the response. Yes, can confirm:
- No Firewall block is occurring (one of the servers is godaddy, and CentOS on godaddy due to Virtuozzo has literally no iptables system running in kernel)
- Again, turning off Cloudflare, site works fine.
- Direct IP to server, no middleware or additional hops whatsoever
- No CDN’s. I can see the 522/524 errors in chrome Network console and they are assets local to the server
- We are using Wordpress, but we are also using Asp.net, and node js apps too. But if you can get a 522 error by manually copy/pasting the failed asset such as : https://mywebsite.com/assets/thing.css , and then turn Cloudflare off, and the same link works, then that’s Cloudflare right?
- I have SSL certs installed on the origin/host, using LetsEncrypt. But of course Cloudflare provisions it’s own top-level global certificate to the browser. Again, i have tried both Flexible and Full modes. Flexible meaning Cloudflare uses [http] instead of [https] when reaching out to origin.
- DNS is all properly configured, no change in over 1.5 years of usage. Suddenly, last 2 weeks – bad.
We have nothing blocking Cloudflare.
And specifically one of the servers literally has no firewall. It’s infuriating, but Godaddy refuses to allow iptables on virtuozza containers (aka their “dedicated hosting plan” ) … problem for another forum.
Point is – there is literally no firewall on the server, and the same problem happens.
Again though, and I must stress , it seems to be random!
It randomly picks which asset to 522/524, and randomly happens throughout the day.
I could get a 524 error right now, but 5 minutes from now you could try the same link and get a different result.
At this point I truly believe there is an issue with Cloudflare’s CDN or distribution system causing this.
Turning off Cloudflare yields good results. Which is bad.