← Back to context

Comment by gwd

10 hours ago

I do appreciate the visual "mea culpa":

Your browser: Working

Host: Working

Cloudflare: Error

Might be the first time I have ever seen that. Though in my case the "Host" is Cloudflare's own Pages service.

  • Yeah, I was shocked. Disbelief that the host was up, which is what usually happens when the cloudflare's page show up

They still blame the customers when you click on "Cloudflare":

> If the problem isn’t resolved in the next few minutes, it’s most likely an issue with the web server you were trying to reach.

  • In terms of probability looking at the history, it is correct. It's mostly me messing up with the web server.

I noticed that refreshing honesty too, not that the users did (our wifi is down fix it pls urgent)

That is really good to be honest!

I have Cloudflare running in production and it is affecting us right now. But at least I know what is going on and how I can mitigate (e.g. disable Cloudflare as a proxy if it keeps affecting our services at skeeled).

I searched my logs for errors for about an hour before figuring out the problem was not on my server :D

That page has special if/endif HTML comments to handle if your browser is IE 6, IE 7, IE 8...