How to Check WordPress Error Logs (Debug Mode)

Where WordPress errors live — three locations

Three locations hold the evidence, each with a jurisdiction:

• wp-content/debug.log — WordPress's own log, written when WP_DEBUG is enabled; the jurisdiction is PHP errors inside WordPress execution.

• cPanel's error_log (Metrics → Errors) — the account-level log covering PHP errors across the account, including ones WordPress never sees.

• Server logs — Apache/Nginx and PHP-FPM logs, visible on VPS tiers or via support on shared plans.

Start with debug.log for plugin and theme behaviour; cPanel's error view for anything the site-level log misses. A stack trace — the lines under 'Uncaught …' — names the exact file and line that failed.

Enabling WP_DEBUG and debug.log (wp-config edit)

1. Open wp-config.php — cPanel File Manager, public_html, edit.
2. Above the 'stop editing' line, add: define('WP_DEBUG', true);
3. Add: define('WP_DEBUG_LOG', true); — this writes errors to wp-content/debug.log.
4. Add: define('WP_DEBUG_DISPLAY', false); and @ini_set('display_errors', 0); — never display errors to visitors; error text leaks paths and sometimes credentials.
5. Reproduce the problem, then open wp-content/debug.log (right-click, View/Edit). Delete the file first for a clean capture of only the new incident.

Fastest technique for intermittent bugs: truncate the log, trigger the bug, read only what the trigger wrote.

Reading the cPanel error_log via Metrics → Errors

On WP_DEBUG, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Decoding common errors — fatal, deprecated, warnings

Fatal error: execution stopped for that request; the page is white or 500. The message's class tells the story — undefined function or class means a missing extension or deactivated dependency plugin; 'Allowed memory size exhausted' means raise limits (the 500 guide walks it). 'maximum execution time exceeded' means a slow loop or import.

Warning: execution continued but something is wrong — 'headers already sent by plugin X' is usually stray whitespace or output before headers in the named file. Notice and Deprecated are informational: notices flag sloppy-but-working code; deprecations flag functions scheduled for removal — your early warning after a PHP upgrade. Deprecated floods after a PHP jump are normal and only need fixing before the next version removes the function.

Turning debug off safely after troubleshooting

Turn debugging off when finished: set WP_DEBUG back to false and remove the other lines, or leave WP_DEBUG_LOG true only on heavily filtered staging environments. The reasons go beyond hygiene: debug.log grows unbounded in public_html and is a known target for attackers who fetch /wp-content/debug.log directly to inventory your plugins and paths.

If you must leave logging on long-term for an intermittent issue, protect the file (deny access to *.log in .htaccess or via the host) and rotate it weekly. And watch disk discipline: an error loop — one plugin writing a warning per page-view — can write gigabytes per day; a sudden quota warning is very often a runaway error_log. Fix the looping cause, not just the file.

Log rotation and disk-space cautions

On error_log in cPanel, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Using logs in a WebJi® support ticket

Allow 80 and 443 to the world, and restrict SSH (22) or RDP (3389) to known IPs. A site that times out after a firewall change is usually a closed web port, not a dead server. If you lock yourself out, use the console in the client area or email support@webji.services before you reboot in a loop.