Find website errors without exposing them publicly

Match a failed request to a timestamp in the Errors screen and application logs.

Where Tools → Metrics → Errors

Before you start

Record the affected URL, time and what you were doing when the problem occurred.
Do not share raw logs publicly; they can contain private paths, identifiers or request data.

1

Match the timestamp and path to your failed request. A warning about another file or an old request may not explain the current problem.
2

If the list is empty, repeat only a safe version of the failing action and check again. Avoid repeating purchases, email sends or destructive actions just to create a log entry.
3

Check the application’s own log and PHP error_log location when relevant. Not every failure is recorded in cPanel’s Errors view.
4

Send support the relevant short excerpt, timestamp and reproduction steps privately. Keep display_errors off on the public site and fix the underlying cause rather than hiding the log.
5

Open Errors and read the recent web-server entries. The screen can also show suEXEC-related errors separately.

Recent web-server and suEXEC errors appear here when available.