• Hello,

    As soon as I activate the plugin, I start getting “500 Internal server error” warning in both admin panel and interface.

    When I check the records in the debug.log field to detect the error, there are only records for a few plugins.

    I disable all the plugins with error logs, but the problem does not improve. Although I checked different plugins that may cause problems later, the result is the same.

    I would like to ask this; Can I detect the error that may cause 500 Internal server error with a different method?

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

    (@johnbillion)

    WordPress Core Developer

    I’m not sure what this could be. It’s possible that an error is occurring inside Query Monitor when it tries to log an error, and this in turn prevents the error from being logged and the server spits out a 500 error.

    Can you add the following to your wp-config.php file and try again?

    define( 'QM_DISABLE_ERROR_HANDLER', true );

    HI,
    I have the same problem, once Query Monitor is activated, but only for the front page (generated via the “front-page.php” template of a custom theme). Both the entire backend and any other page in the frontend are visible and navigable (I navigate directly via URL in the address bar). No error log is present in the “debug.log” file.
    I have already tried to insert the above indication

    define( 'QM_DISABLE_ERROR_HANDLER', true );

    into the “wp-config.php” file but without success.

    Any other suggestions?

    Thank you

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘500 Internal server error’ is closed to new replies.