Error 520 - my website is down

My site is down,
I try to access my site but it’s down for more than a few hours.

I checked all the processes and everything seems to be working fine.

My site is https://gringo.co.il.

It says:
There is an issue between Cloudflare’s cache and your origin web server.

First I thought it’s something related to my DB, but I connected remotly and it works fine, checked all services in my site and they are fine.

I even tried to get an image from the site and I get the same error:
https://images.gringo.co.il/location/4c581d78-b5cc-4162-9363-575fc764e878_20180712_173231/1982x1487_4c581d78-b5cc-4162-9363-575fc764e878_20180712_173231.jpg

please help me, it’s urgent!

From what I seem to be able to tell it seems that error comes straight from your server. Check there first.

I checked everything and couldn’t find any error including SQL,Nginx and my application.

Then I Restored the Droplet from DIGITAL OCEAN to what is was 14 hours ago when everything still worked fine and it’s still not working so the only conclusion is that somethings between Cloudflare and my site went wrong.

That wont be database related. Check you server logs.

Do you feel comfortable sharing your server IP address here?

By server logs do you mean nginx logs? because I already checked them and couldn’t find anythings.

I thought that it is connected to the Database because I was working on it, but I can connect to the database from my local machine, but I cannot serve an image.

Whatever is running at that address doesnt return anything at all. It accepts the connection but then immediately closes it, respectively times out.

I can move the name servers to Ezoic and check if it will work there, but that could take a few hours, do you have any way to check if it’s Cloudflare related issue?

That is not a nameserver issue. The issue is your webserver, you need to make it properly responds to requests. I’d advise against changing nameservers.

1 Like

Look at this:
https://images.gringo.co.il/banners/3/insurance-comparing.jpg

This returns the image…

The error message is like this:

There is an issue between Cloudflare’s cache and your origin web server. Cloudflare monitors for these errors and automatically investigates the cause. To help support the investigation, you can pull the corresponding error log from your web server and submit it our support team. Please include the Ray ID (which is at the bottom of this error page).

The SQL server I run on the server works fine, the application seems to work fine as well, nginx serves some images and some images not, but not the application it self…

So we can be sure it’s something related to nginx, but when I checked the error log I couldn’t point at something…

I just logged in to my Ezoic dashboard and this is the message they have:

Since I my name servers are at cloudflare I am guessing this issue is regarding to Cloudflare.
@sandro

Which error message?

Again, the server in question does not respond. This is not a Cloudflare issue.

How it’s possible that this image is served well:

But not this image:
https://images.gringo.co.il/location/c6b054f7-3fc4-4004-961c-452825984e56_cartagena_light_house/c6b054f7-3fc4-4004-961c-452825984e56_cartagena_light_house.jpg

Also I just got this from Ezoic Dashboard:

My app is running,db is running, nginx is running, I don’t know where is the problem.

The error message I pasted is from the Error 520 page shown here:
https://images.gringo.co.il/location/c6b054f7-3fc4-4004-961c-452825984e56_cartagena_light_house/c6b054f7-3fc4-4004-961c-452825984e56_cartagena_light_house.jpg

Because you must have made some changes or fixed something else, as your server now responds properly and should work via Cloudflare too.

What is your encryption mode on Cloudflare? Flexible? If so, switch that to “Full strict”.

The “Working image” comes from Cloudflare cache I am guessing because:
https://images.gringo.co.il/banners/3/insurance-comparing.jpg?v=1
is not working


SSL is always on Full(strict)

Hmm, in that case it should work. My best guess would be that you either have a firewall or something similar in place which either blocks Cloudflare altogether or rate-limits it.

Again I can only advise to go through your whole configuration and make sure Cloudflare can connect without issues. Check all logs.

I found the problem!

I went to DNS records in my Cloudflare dashboard and saw that EZOIC changed them all without letting me know.

All the dns records pointed to EZOIC servers, after I changed that back to what it used to be(thanks good I have a screen shot of it), it returned to work again.

Thank you Sandro

@sandro
Cloudflare should investigate this issue.

When I started with Ezoic they asked me to change the name servers to their’s, but also asked me for my username and password to the cloudflare dashboard, how come Cloudflare is ok with this?