> ## Documentation Index
> Fetch the complete documentation index at: https://help.noxity.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> Read the last ~300 entries from the Apache and PHP error logs without downloading the file.

The Errors tool shows the last \~300 entries from your account's combined Apache and PHP error log. First place to look when a page returned a 500 or a script silently failed.

<Frame caption="cPanel home → Metrics → Errors">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/noxity/images/cpanel/metrics-analytics/errors/page-light.png" alt="Errors tool with recent log entries" className="block dark:hidden" />

  <img src="https://mintlify.s3.us-west-1.amazonaws.com/noxity/images/cpanel/metrics-analytics/errors/page-dark.png" alt="Errors tool with recent log entries" className="hidden dark:block" />
</Frame>

## What you'll see

A reverse-chronological list of error events. Each row carries:

* A timestamp in server time.
* The domain or vhost where the error fired.
* The level: `[error]`, `[warn]`, `[notice]`.
* The message itself, often with file path and line number.

The most common entries on a real site:

| Pattern                                                              | Usually means                                                                                               |
| -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| `PHP Fatal error: Uncaught ... in /home/user/public_html/...`        | Your code crashed. The line number points at the exact spot.                                                |
| `File does not exist: /home/user/public_html/wp-content/uploads/...` | A 404 on a missing image or asset. Loud but rarely fatal.                                                   |
| `client denied by server configuration`                              | An `.htaccess` rule blocked the request. Useful when debugging WAF rules.                                   |
| `Premature end of script headers`                                    | A CGI/PHP script crashed before sending a response. The next entry in the log usually has the actual error. |
| `Permission denied: ... .htaccess pcfg_openfile`                     | The webserver can't read an `.htaccess`. Almost always a chmod problem.                                     |

## What it's good for

* Reproducing a 500. Trigger the page, refresh the error log, the new line at the top is your error.
* Catching warnings WordPress is hiding. Many themes display a clean page on the front end while quietly logging deprecation notices.
* Sanity-checking after a deploy. Push, hit the site, check the log. If new errors appear, roll back.

## What it's not

* Not the access log. Successful requests don't appear here. For traffic, use [Visitors](/web-hosting/cpanel/metrics-analytics/visitors).
* Not the mail log. SMTP failures live in [Track Delivery](/web-hosting/cpanel/email-management/track-delivery).
* Not exhaustive. Past the 300th line, older errors fall off. For longer history, configure log archiving in [Raw Access](/web-hosting/cpanel/metrics-analytics/raw-access) or open a ticket.

<Tip>
  PHP errors only appear here if PHP's `log_errors = On` and `error_log` is unset (or set to the system default). cPanel ships with both correct out of the box, but custom `php.ini` files can break the chain.
</Tip>

## Common issues

<AccordionGroup>
  <Accordion title="The error log is empty but the site shows 500">
    Check that `display_errors` and `log_errors` are both on in PHP. If a custom `error_log` path is set in your `.htaccess` or `.user.ini`, errors are going there instead. Also check for a `wp-content/debug.log` if you're on WordPress with `WP_DEBUG_LOG = true`.
  </Accordion>

  <Accordion title="I see thousands of 'File does not exist' lines for /favicon.ico">
    Browsers automatically request `/favicon.ico` on every page. Add a 1×1 transparent PNG at that path or set a 404-pass rule in `.htaccess`. The errors are noise but they crowd out the ones you care about.
  </Accordion>

  <Accordion title="Errors mention a path I don't recognise (mod_security)">
    Our [ModSecurity](/web-hosting/cpanel/security-settings) WAF logs blocked requests here. If a legitimate request is being denied, the message includes a rule ID. Quote that ID to support and we can whitelist it.
  </Accordion>
</AccordionGroup>

## Need a hand?

<CardGroup cols={2}>
  <Card title="Open a ticket" icon="life-ring" href="https://members.noxity.io/submitticket.php">
    Best for anything that needs an account check or a config change on our end.
  </Card>

  <Card title="Live chat" icon="messages" href="https://noxity.io/contact">
    Faster for quick questions during business hours.
  </Card>
</CardGroup>