Divi WordPress Theme
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WordPress fix Weird Bug: WP_DEBUG Set to FALSE Kills Site

Discussion in 'Misc WordPress Requests' started by conrmahr, Dec 11, 2017.

  1. conrmahr

    Guest

    Weird Bug: WP_DEBUG Set to FALSE Kills Site, by conrmahr

    Looking for some advanced help to troubleshoot this very odd heisenbug-like issue. It seems backwards, but I have a 4.8.4 WordPress instance on a RHEL6/httpd server behind a corporate load-balancer (F5) that I have to set WP_DEBUG to false or I will get this error:


    This site can’t be reached
    The connection was reset.

    Things I’ve tried so far unsuccessfully:
    – Fresh install
    – Deactivate all plugins
    – Set php error reporting to none, E~ALL, default
    – Increased PHP memory limit

    Only modifications I’ve done to wp-config.php:

    define('WP_DEBUG', true);
    define('FORCE_SSL_LOGIN', true); // Added for forced https
    define('FORCE_SSL_ADMIN', true); // Added for forced https
    define('OPENID_SSL', true); // Add for wordpress-openid plugin

    Any guidance on what to troubleshoot would be much appreciated!

    Weird Bug: WP_DEBUG Set to FALSE Kills Site
     
    #1

Share This Page

Monarch Social Sharing Plugin