How to View Your Website's Error Logs

Find and read your site's error logs in cPanel to diagnose 500 errors, broken scripts, and other server-side problems.

· Updated · 2,563 views

When a page shows a blank screen or a 500 error, the error log usually explains why. cPanel exposes the most recent server errors so you can find the cause quickly.

The Errors Tool

  1. In cPanel, open Errors under the Metrics section.
  2. The page lists the most recent error log entries, newest first.
  3. Each line shows a timestamp, the visitor IP, and the error message with the file and line number.

This view holds only the latest entries, so check it soon after a problem occurs.

Reading an Entry

A typical PHP error looks like this:

[date] [proxy_fcgi:error] PHP Fatal error: Uncaught Error:
Call to undefined function my_func() in /home/cpuser/public_html/page.php:42

The important parts are the file path and the line number, here page.php line 42. Open that file in File Manager to inspect the problem.

Finding More Detail

The Errors tool is a summary. For a fuller record:

  • Some applications keep their own log, such as wp-content/debug.log in WordPress when debugging is enabled.
  • Check the Raw Access logs under Metrics for the full request history.
  • Look in your home directory for an error_log file inside the affected folder, which PHP writes automatically.

Common Causes

  • A fatal PHP error from a plugin or custom code.
  • A .htaccess syntax mistake causing a 500 error.
  • Exhausted memory, shown as an "allowed memory size" message; raise memory_limit in MultiPHP INI Editor.

If the log points to a file you did not change, a recent plugin or theme update is the likely cause. Disable it and re-test.

Was this article helpful?

Your feedback helps us improve our documentation.

Still Need Help?

Our support team is available 24/7 to assist you.