1

Any advice for debugging a 520 error from Cloudflare?

I know this isn’t SO but Ive been having the toughest time finding a decent way to find the cause of a 520 error from Cloudflare.

I have a droplet of Digital Ocean running Apache 2.4X and randomly throughout the day I will get 520 errors in the browser’s Networking log.

Naturally, there’s nothing even noted in the Apache error log or access log. And Cloudflare has no logs on this in the console.

If I retry the request it will go through with no problem.

Anyone experienced something like this?

Comments
  • 0
    If @FrodoSwaggins says not to use cloudflare, you should listen.
  • 0
    @FrodoSwaggins Too late. It’s already deeply integrated into all of my “infrastructure”.

    Looks like a couple 520 errors a day is going to be the new norm.
  • 0
    @FrodoSwaggins and how often are most services hit by ddos's? Basically never. And what damage does it do? Often nothing at all.

    It's insurance against catching a cold.
    And it's free; all you have to do is let someone watch and record every move you make, every sentence you utter, every word you write.
  • 1
    The solution is timestamped logs on the server end, full verbosity, then see what happened.
  • 0
    You have a plugin that causes your website to return over 10 headers.
Add Comment