Please help with error 520

I got 520 error. I contacted godaddy and they said this error i need to contact Cloudflare to fix it.
I can access the website by pressing f5 many times but i think this error is really serious. Ahrefs gave my website 0 points. Please help me to fix it, thanks.

My website: forexuytin.com

Was your website working properly in HTTPS before you add Cloudflare?

2 Likes

Sugerencia:

  1. Sigue estos pasos:
  1. Prueba que tĂş sitio funciona sin Cloudflare.

I didnt have https before, Godaddy told me the problem beacause of Cloudflare, I need to remove Cloudflare nameserver and use theirs, but my website can not access without https, Please help. I am not enough money to pay for ssl certificate.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

Hi @dinhnguyenhoanganh19,

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.

https://support.cloudflare.com/hc/en-us/articles/115003011431-Troubleshooting-Cloudflare-5XX-errors#520error

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.com/cdn-cgi/trace - replace example.com with 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 ?
1 Like

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: