520 Errors prevent backend access

  • For the last week or so, Cloudflare 520 errors have made the backend of one of our sites unusable. Either the main CF 520 error screen shows up, or the WP backend partially loads with broken CSS/JS files.

    Cloudflare has been working great for months – this is a new issue. I’ve reached out to the host and Cloudflare Business support, but am hoping for any ideas here as well.

    We’ve been using page rules with no caching applied to wp-admin. Today I switched to Workers with no change yet.

    The site is on a dedicated 4GB DO droplet. Memory and CPU look just fine.

    Site Error logs: nearly empty. Nothing relevant showing up at all.

    Pausing Cloudflare makes the site work again.

    What else could I try? Thank you

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi @razorfrog,
    sorry for the delayed reply. Generally speaking, the CF 520 error comes when the origin host is unreachable. I think you should check the server access log to see if some server-level firewall is blocking the Cloudflare requests.

    @razorfrog Have you discovered a permanent fix for this yet? We’ve had the same issue as of a few days ago. Everything you described – sometimes 520 page, sometimes partially loaded content, nothing in server logs and running on 4Gb droplet with no spike in CPU or anything. Only wp errors seem to be from scripts that only partially run before being cut short.

    Thread Starter Razorfrog Web Design

    (@razorfrog)

    @isaumya Thanks for the reply. Nothing in the logs. I’m working with the host and Cloudflare but so far haven’t had any luck.

    @amartini Not yet. I’ll try to report back here with any findings.

    Mat

    (@mateithemeisle)

    Hello @razorfrog and @amartini ,

    Here are some resources that might come in handy for your hosting provider. You can check these and see if they help in any way.

    Thank you and please let us know if you managed to find a solution!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘520 Errors prevent backend access’ is closed to new replies.