Cloudflare causing 520 errors on multiple websites

Hi, I’m having multiple websites running at Cloudflare and all of them are having 520 when running through Cloudflare. Using the origin host works fine. Seems related to The Netherlands because it’s happening at all Dutch websites and seen other users posting similar problems with their Dutch website.


Can you guys check re-route traffic or fix this in another way?

I’m not getting an error on the site you mentioned. Loads fine for me :slight_smile:

Hi @jeffrey1,

A 520 error occurs when the connection started on the origin web server, but that the request was not completed. The most common reason why this would occur is that either a program, cron job, or resource is taking up more resources than it should causing the server not to be able to respond to all requests properly.

Review the Quick Fix Ideas in this Community Tip for troubleshooting suggestions.

I see this on the site:

This page isn’t working took too long to respond.


I’m getting this:

How can I reproduce that 504?

I’ve been running against the origin website by changing my hosts file (Windows) and can run the site fine without any interuptions.

Also, could this have something to do with it?

Looks like it is region bound. Anyway, in the meantime it looks like it’s working a lot better now. Seems resolved for now.

And it’s back. Issue is appearing in waves.

Location Slough, United Kingkom keeps failing almost every single time.

Would you feel comfortable sharing your server’s IP address here?

One origin server ip is And another origin server at another host is

So you have two A records? The first one seems to serve your site, the second one doesnt. Though that shouldnt be necessarily the reason for the error, just a reason for different content. Could it be that one machine is configured to block certain Cloudflare requests? For starters I’d remove one A record to check if the issue disappears. Then switch to the other and check again.

On a related note, your servers are not configured for SSL, hence you cant have a proper HTTPS connection. You should fix that.

yes, a wildcard and a www, but they point to the same single server/machine.

I know I have not SSL, it wasn’t supported at the host (shared provider) at the time, but SSL flexible works just fine for me.

Anyway, we’re still experiencing this issue. Contacted the provider already, but there is no block. And I and other people from the Netherlands are experiencing the same thing over several dutch websites connected to Cloudflare and we’re all using different hosting parties.

They might point to the same machine, but if the address is different the routing can be too and that might be the reason for the error.

As for SSL, Flexible is highly discouraged as it breaks your encryption and makes your site insecure.

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