How to find the cause of website errors using the error log in Plesk

When a website suddenly stops loading, displays a “white screen,” or returns a server error code, the main tool for troubleshooting becomes the error log. In this practical guide, we will review the main types of server errors, learn how to find and read logs in the Plesk hosting control panel, and look at basic steps to quickly restore your resource’s operation.

1. Differences Between Common Server Errors (500, 502, 504)

Before opening the logs, it helps to understand what each web server response code actually means:

  • 500 Internal Server Error: The most common error. It indicates that a critical PHP error (Fatal error) occurred in the site’s code, a malfunction happened in the .htaccess file, or the RAM limit (memory_limit) was exceeded.
  • 502 Bad Gateway: Occurs when the frontend server (Nginx) does not receive a valid response from the backend (Apache or PHP-FPM). Often caused by a PHP process crash or CPU time limits exhaustion.
  • 504 Gateway Timeout: Means the server is taking too long to process the request and cuts off the connection due to a timeout. This usually happens due to heavy database queries, slow external API requests, or infinite script loops.

2. How to Open Logs in the Plesk Panel

Plesk has a convenient built-in log viewer that allows you to track events in real-time without needing to connect via FTP or SSH:

  1. Log in to the Plesk control panel (via your RX-NAME billing client area).
  2. In the Websites & Domains section, find the required domain.
  3. In the domain management tools block, click on Logs.
  4. A page with web server events will open. To see only critical failures, uncheck informational entries (such as Access) and leave only the Apache error, Nginx error, and PHP filters active.
  5. To track errors live, click the Start real-time updates button, and then refresh your website page in a neighboring browser tab.

3. How to Read a Log Entry and Find the Culprit

A typical critical error string in the Plesk log looks roughly like this:

[Mon Nov 16 02:10:15 2026] [php:error] [pid 14820] [client 192.0.2.1:54321] PHP Fatal error: Uncaught Error: Call to undefined function… in /var/www/vhosts/domain.com/httpdocs/wp-content/plugins/broken-plugin/index.php on line 42

What to look for when analyzing such an entry:

  • Message Type: Look for the words Fatal error or Parse error — these are what stop the website from loading. Warnings (Warning) or notices (Notice) usually do not completely “break” the page.
  • File Path: The fragment after the word in points to the exact location of the problem. For example, if the path features /wp-content/plugins/plugin-name/ or /wp-content/themes/theme-name/, the cause is a specific CMS extension or template.
  • Line Number: The reference on line 42 helps the developer quickly locate the error in the code.

Quick fix for plugins/themes: If the log points to a specific plugin, go to Files in Plesk, open the wp-content/plugins/ directory, and temporarily rename the problematic plugin’s folder (for example, by adding _old to its name). This will forcibly deactivate it and restore access to the site.

4. Basic Steps in Plesk to Restore Website Operation

If the error log shows syntax incompatibility messages (e.g., syntax error, unexpected...) or memory exhaustion, perform the following settings in Plesk:

  1. Changing the PHP version and selecting the PHP-FPM handler:
    • In the Websites & Domains section, click PHP Settings.
    • Try switching the PHP version to a newer one (e.g., PHP 8.1, 8.2, or 8.3) or, conversely, revert to the previous version if the failure occurred right after an update (some older plugins do not support newer PHP versions).
    • In the Run PHP as field, choose FPM application served by Nginx or FPM application served by Apache — the PHP-FPM handler runs significantly faster, more stably, and manages memory more efficiently under load.
  2. Increasing the memory limit (memory_limit):
    • If the logs show an Allowed memory size of ... bytes exhausted error, on the same PHP Settings page, increase the value of the memory_limit parameter (e.g., to 256M or 512M) and click Apply.

What to do if you cannot fix the issue on your own?

If you reviewed the error log but the cause of the issue remains unclear or requires server administrator intervention, our support team is ready to help you 24/7. Contact us through any convenient channel:

  1. Online Chat on the Website: Write to us in the chat widget directly on our website (the fastest way to get a response and share the log fragment).
  2. Telegram Bot / Chat: Contact our support team on Telegram for prompt assistance.
  3. Email: Send a detailed email with your domain name and the copied error text from the log to technical support.
Leave a Reply 0

Your email address will not be published. Required fields are marked *