bro. I changed it to flexible… Now i see some improvement. Now what to do nexT?
Why would you do something which was already explicitly discussed and advised against?
Set it to Full Strict and only Full Strict.
What do you mean by improvement?
As Sandro pointed out, this situation of using ‘Flexible’ is not ideal and not completely secure. It would appear that the problem is with your encryption certificate (assume that your hosting company Namecheap manages it) and you need to advise them that Cloudflare is unable to connect to your server while using it. Maybe a misconfiguration on their part.
To be precise, not secure at all.
Bro when Attached my domain with cloudflare. I done exactly proper settings. But 3 days ago i signed up for Ezoic ad and ezoic auto integrates some setting and from that point my website is not performing well
So before you used Ezoic, everything was working fine with your website with encryption set to “Full”? No 520 errors?
Well firstly set your encryption back to Full or Full Strict. It would appear that Ezoic requires additional configuration to work behind Cloudflare. I have no experience with Ezoic but I did google it and found a page that gives a basic overview of how to make it work with Cloudflare.
If this is beyond your skillset, I would ask your provider to review or start a new post in the support community here.
Are you saying from a security point of view, “off” and “flexible” are identical?
Yes, they are, both transfer data via HTTP and have no encryption.
Due to the number of 520s being reported in similar circumstances, we are escalating the issue to Cloudflare Support. The original incident should have been resolved and your issue may well be unrelated.
We recommend checking these troubleshooting tips, if you haven’t already.
If you have been through these thoroughly and are not seeing corresponding issues on your network/server and you have a ticket number with Cloudflare, please reply and post that #.
To enable efficient troubleshooting by support, please ensure you include the following on the ticket:
- example URL(s) where you are seeing the error
- Ray IDs from the 520 pages
- output from a traceroute from any impacted user
- output of
example.comwith the affected domain.
- Also include two HAR file(s) : one detailing your request with Cloudflare enabled on your website and the other with Cloudflare temporarily disabled - see How do I temporarily deactivate Cloudflare ?
So as part of https://community.cloudflare.com/t/random-520-errors/ we fixed an issue with origins silently ending a keepalive connection that was causing very rare 520 errors.
Thus we recommend testing again - if you still see 520s - make sure you follow the guidance in our community tip here: