On the shared free SSL, I am getting 520 error on my website

When I am changing the nameservers to custom nameservers, I am getting a 520 error where the host is not responding.

When I am porting back to the domain’s default nameservers, it is working.

When I check the A mapping with the custom nameservers in DNS in who.is, I see there are 3 different mapping for my website. Which changes when I revert back to Godaddy’s default nameservers.

Please help.

Kindly, may I ask you to:

  1. What is your domain name?
  2. To use Cloudflare, you need to add a Cloudflare account
  3. Under your Cloudflare account, you need to add your website/domain
  4. In the process of adding a website, you would be given the Cloudflare nameservers
  5. Change your nameservers for your domain at your domain registar to Cloudflare ones (GoDaddy?)
  6. Wait for few hours due to DNS propagation

Regarding the 520 error you managed to get, were the A records :orange: or :grey:?

Also, may I ask if you have already checked with the steps as written from below article?:


Is the domain pointed to Cloudflare nameservers?

Have you checked your web server log files and firewall?

Do you use any other CDN with Cloudflare?
Do you use any CMS like WordPress?
Do you already have an SSL certificate installed at your origin/host for your Website(s)
(domains and sub-domains)?
Have you got CNAME or A records for your domains pointed to your origin/host IP address at Cloudflare dashboard?

Who is the hosting provider?

Are the needed one and compatible ports with Cloudflare openned at the Origin/Host/Server and apps running on them (and not on the incompatible ones)?


Is Cloudflare allowed to connect to your origin/host?

These are possible Cloudflare IP addresses if your A www or A yourdomain.com records at Cloudflare DNS dashboard are being proxied via Cloudflare (:orange: cloud).

Thank you so much fritexvz for your reply.

My domain name is sauravmukherjee.com

I have been using a Cloudflare account for some time now, and I have my domain added to it and have the nameservers changed on Godaddy.

DNS and everything were working fine for the last few months, only today it started throwing 520 for some reason.

I see. So, those were the proxy IPs. I understand now. I did not see them in the Cloudflare dashboard, but saw them at who.is

Final thoughts, I unlinked everything from Godaddy and relinked everything. It seems to be working for now like it was for the past few months. I don’t know what I changed to actually make this work.

1 Like

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