What is the name of the domain?
What is the error number?
What is the issue you’re encountering
522 Error
What steps have you taken to resolve the issue?
Tried trouble shooting using the AI but still issues.
522 Error
Tried trouble shooting using the AI but still issues.
Im also experincing the same thing and multiple people on netlify as well. They are saying its on cloudflare end. here is the forum on neltify Sites down, Awaiting Netlify DNS - #22 by Josephadam - Support - Netlify Support Forums
If you temporary enable the “Pause Cloudflare” option, does the Website respond normally via HTTPS or maybe the SSL certificate needs to be renewed?
I am also experiencing this issue, see:
I have done absolutely everything I can to eliminate a configuraton error on my part but simply cannot find any evidence whatsoever that Cloudflare is attempting to connect the origin server on either of the correct addresses. Connecting via DNS (with proxy switched off) works flawlessly but as soon as the Cloudflare proxy is switched on, Cloudflare attempts to connect to something (not my origin server) and times out.
I have checked the NACL configuration on the origin server - completely unchanged - as compared to exactly the same origin server that was successfully configured with a different cloudflare host.
I have checked and verified the correct operation of the listener rule on the origin server - with proxy switched of DNS resolution and traffic flows through the origin server to backend servers behind.
I have exhausitvely checked the vpc flow logs and can see no evidence of attempt ingress (rejected or otherwise) by the cloudflare proxy into the origin server. I repeat exactly rhe same diagnostic on working pair of cloudflare proxy and origin server (which share the identical terraform configuration, bar necessary concrete differences) and do detect ingress by the cloudflare proxies - so the test methodology is correct
I have even rolled backed the host I am trying to migrate to its original settings and they all work.
There is something wrong with the new settings. I have tried to contact Cloudflare support. They were hyper-responsive - they marked my case resolved within nanoseconds of its being opened and without taking even single moment to consider my problem let alone devote a microsecond of effort to providing a useful response.
I’ve replied to your topic about your case. Please reply further there to keep the posts organized under the correct threads. Thank you in advance.
See the update on my linked problem below (follow the link). A TLS/SLS configuration error in the cloudflare console can cause HTTP 522 errors that are completely unrelated to any configuration issues in the origin server.
Please check that you have done something other than accept the default (unconfigured) “Encryption Mode” in the TLS/SSL settings. In my case the defaults resulted in no traffic flowing to the origin server network and resulting in the misleading 522 error - once I corrected the configuration to the intended values, the connections worked as intended.
And note, there may be a difference between:
I do not know that there is a difference, All I know the broken configuration was the implicit, never configured state and it started working when I applied the configuration appropriate to us (which happens to be Full (Strict)). Readers need to research exactly which option is suitable for them.
The key point is that failure to configure this can result in TLS/SSL related configuration errors that present ONLY as HTTP 522 errors and never in any other way (such as an invalid certificate errors visible in the browser). In the presence of this misconfiguration there is literally nothing in the Cloudflare console or Cloudflare documentation that will explain that the 522 error MAY be caused by missing TLS/SSL configuration
Hi, i tried changing the settings to default and still facing the same 522 error
Ok that’s a shame - it would be worth reviewing, in detail, your end to end SSL configuration - default may not be correct for you.
We have valid certificates on our origin server so Full (Strict) was the right value for us. What definitely did not work was leaving it completely unconfigured (which may, or may not be different to an explicit configuration of default - I literally have no idea)
This topic was automatically closed after 15 days. New replies are no longer allowed.