When a website encounters an issue—such as a 500 Internal Server Error, a blank white screen, or a critical application failure—checking web server and application logs in Plesk is the fastest way to diagnose the root cause.
Plesk centralizes HTTP, HTTPS, Apache, Nginx, and PHP error logs into a single interface so you can quickly pinpoint broken code, missing files, or resource limitations.
Steps to Check Logs in Plesk
1. Access Your Domain Logs
- Log in to your Plesk Control Panel.
- Go to Websites & Domains in the main menu.
- Locate your domain and click on Logs.
2. Filter and Review Messages
Use the Log Options dropdown menu (top right) to toggle specific log types:
- PHP Errors: Captures fatal errors, syntax mistakes, missing functions, and memory limits.
- Apache / Nginx Errors: Captures web server issues, execution timeouts, missing files (404), and permission blocks (403).
- Access Logs: Tracks incoming web traffic and HTTP status codes.
Identifying Key Details in Log Entries
When reviewing an error entry, look for these three key components:
| Element | Example | What It Tells You |
| Timestamp | [22-Oct-2026 14:15:02 UTC] |
Matches the log entry to the exact time you tested or saw the error. |
| Error Level |
PHP Fatal error or [error]
|
Distinguishes critical site-breaking failures from minor warnings. |
| File Path | /httpdocs/wp-content/plugins/... |
Shows the exact file, line number, and plugin/theme causing the crash. |
Common Error Examples & Fixes
1. PHP Fatal Error
- Sample Log:
PHP Fatal error: Uncaught Error: Call to undefined function... in /httpdocs/wp-content/plugins/sample-plugin/plugin.php on line 42
- Cause: Incompatible plugin, broken theme file, or PHP version mismatch.
- Fix: Rename or disable the plugin folder listed in the path via File Manager/FTP, or adjust your PHP version under PHP Settings in Plesk.
2. Memory Limit Exhausted
- Sample Log:
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted...
- Cause: A script or plugin exceeded the allocated PHP memory limit on the server.
- Fix: Contact our customer support team to request a memory limit increase for your hosting plan or account.
3. Permission Denied
- Sample Log:
[error] ... open() "/httpdocs/index.php" failed (13: Permission denied)
- Cause: Incorrect file or directory permissions preventing the web server from reading files.
- Fix: Reset file and folder permissions using the Plesk File Manager.
Additional Resources: For technical details on log file locations, log rotation settings, and downloading raw log archives, refer to the official Plesk Log Files Documentation.
Comments
0 comments
Please sign in to leave a comment.