Latest update broke site

  • Just updated a multisite to the latest version of CLoudflare. Immediately the site was down “bad gateway” Cloudflare error

    I had to remove the plugin via FTP, and the site came straight back

Viewing 4 replies - 1 through 4 (of 4 total)

  • Hi danbrady,

    – Could you send the error logs?
    – Could you verify your Cloudflare plugin version?
    – Could you read your PHP version?

    This also occurred for our site last night, but I was able to respond quickly as I knew the culprit due to it being what I just updated. I feel for those with auto-updates, or who aren’t tech savvy, as that update takes sites offline, and many WordPress admins are laymen.

    I see you have now issued a fix.

    Did you guys do NO QA? Can you elaborate on why we should use this plugin at all? CloudFlare is awesome, but I am not subjecting my site to a plugin that will take the whole site down on any random update.

    p.s. Our setup is PHP 5.5.9 and latest WP. But seems like you already discovered the issue.

    • This reply was modified 8 years, 6 months ago by bitsum.
    Thread Starter danbrady

    (@danbrady)

    php 5.6
    the offending cloudflare plugin was Version: 3.0.1

    I can’t see anything useful in the error log

    Hi @bitsum,

    We did a lot of QA on this latest release. It was in beta for about a month with over 55 beta testers. The root cause of the 520 and 502 http error codes was because our implementation of HTTP2/Server push created too many headers for websites with lots of resources to load. We never saw this during testing because by chance none of our beta testers had front ends large enough to trigger the header bug.

    Thanks,
    John

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Latest update broke site’ is closed to new replies.