Forum Discussion
NimbostratusWordPress WP_DEBUG Set to TRUE to Work
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 has the certificate installed on it. If I have WP_DEBUG set to false in the code, which is the default setting, I will get this error:
This site can’t be reached The connection was reset.
Any guidance on what how to troubleshoot it on the F5? It only happens in the Prod environment. We have DEV and CRT environments that use self-signed certs and it works fine.
From your description my guess would be that the monitors fails when you do this. If you have HTTP monitors with receive strings I'd recommend testing to see if the condition is fulfilled after removing the word press from debug mode.
Another possible thing is that the word press site might simply refuse to start. Have you tried to browse it locally?
