QM + Cloudfront + 520 Error

  • Hi, I spent the greater part of a day pulling my hair out troubleshooting a 520 error in wp-admin with my new Cloudfront (I tried Cloudflare also) distribution.

    I noticed that admin-ajax took a long time to load and it ended up giving me the 520 error due to OriginHeaderTooBigError, I did notice that admin-ajax would take around 5-6s to run and realized when checking the error out on my origin url that QM would load just as soon as the ajax script finished running.. so I disabled it and it all started working

    I have a bunch of PHP deprecated errors that I don’t really want to see every time I load a page, I noticed that we can turn off PHP errors but can we narrow that down to only the deprecated messages?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    I’ve had quite a few similar reports of this lately, I’m guessing there are just too many deprecated PHP errors on sites that are upgrading to newer PHP versions.

    I will look into introducing an option to control some of the error handling.

    In the meantime, if this is preventing you from using Query Monitor you can set this constant in your wp-config.php file to disable its PHP error handling:

    define( 'QM_DISABLE_ERROR_HANDLER', true );
    Thread Starter tommmoe

    (@tommmoe)

    Thanks John, keep up the good work! QM is a great tool!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘QM + Cloudfront + 520 Error’ is closed to new replies.