EN

Web hosting

Read the logs to diagnose a 500 error or a blank page

Find the cause of a 500 error or a blank page with the Plesk logs: open them, read an error line and fix the most common messages.

6 min read, updated on 18 November 2026

On this page

A 500 error or a blank page only tells you that something went wrong on the server. The exact cause is almost always in the logs. This guide shows you where to read them, how to interpret an error line and how to fix the most frequent cases.

What you need

Open the logs

  1. Log in to Plesk and open Websites & Domains.
  2. Find the domain concerned. A subdomain has its own logs.
  3. Click Logs, in the developer tools.
  4. In the log selector, keep at least Apache error and nginx error.

If this button is not available, open File Manager (or Files), then the Logs folder, and click error_log.

File Content Use
error_log Apache errors and, in most cases, PHP errors The first one to check
proxy_error_log nginx proxy errors 502 and 504 errors, timeouts
access_log / access_ssl_log HTTP and HTTPS requests handled by Apache See which addresses were called and with which status
proxy_access_log / proxy_access_ssl_log Requests handled by nginx Same use, on the proxy side

Catch the error as it happens

  1. In Logs, click Start real-time updates.
  2. In another tab, reload the failing page.
  3. Go back to the logs and read the lines that have just appeared.
  4. If there are several, start with the first in the series: the others are often a consequence of it.

To view or download a full file, click Manage Log Files.

Understand an error line

Text
[Wed Nov 18 10:42:07.123456 2026] [proxy_fcgi:error] [pid 12345] [client 203.0.113.10:51234] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught Error: Call to undefined function my_function() in .../httpdocs/index.php:12'
Part Meaning
[Wed Nov 18 10:42:07...] Date and time, in the server's time zone
[proxy_fcgi:error] Component involved and severity level
[client 203.0.113.10:51234] Address of the visitor who made the request
PHP Fatal error Type of error
Call to undefined function my_function() Description of the problem
.../httpdocs/index.php:12 File and line to examine

Fix common errors

Log message Cause What to do
PHP Parse error: syntax error, unexpected ... Syntax error in a PHP file Fix the line shown, or restore the previous version of the file
PHP Fatal error: Uncaught Error: Call to undefined function ... Missing function: PHP extension not installed, file not loaded, or code incompatible with the PHP version Check the version under PHP Settings and update the plugin or theme involved
PHP Fatal error: Allowed memory size of ... bytes exhausted Memory limit reached Look for the plugin responsible, then raise memory_limit if the option is available
PHP Fatal error: Maximum execution time of ... seconds exceeded Script ran too long Optimize the task, then adjust max_execution_time if the option is available
mod_fcgid: read data timeout PHP did not respond in time Same approach as for execution time
Request exceeded the limit of 10 internal redirects Rewrite loop, often in .htaccess Temporarily rename .htaccess to confirm, then fix the rules
Invalid command '...', perhaps misspelled or defined by a module not included in the server configuration Invalid or unsupported directive in .htaccess Remove or fix the line quoted
Option FollowSymLinks not allowed here The server configuration forbids this option in .htaccess Remove it from .htaccess to test, then contact support if the site needs it
Permission denied or pcfg_openfile: unable to check htaccess file Incorrect permissions on a file or folder Restore standard permissions, usually 644 for files and 755 for folders
upstream timed out in proxy_error_log The application server responds too slowly (504 error) Identify the slow page or task

Blank pages

A blank page is often a fatal PHP error with error display turned off, which is normal in production. Check error_log first.

If nothing appears there, check the following:

  • Did an update, a new plugin or a PHP version change happen just before? Roll it back to test.
  • Under PHP Settings, the View the phpinfo() page link shows the active values, including log_errors and error_reporting.
  • Does your application keep its own log?

Turn on the WordPress debug log

In wp-config.php, add these lines above the That's all, stop editing! comment. If some constants already exist, change them rather than duplicating them.

PHP
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Reload the page, then read wp-content/debug.log. To isolate a plugin, rename its folder in wp-content/plugins and test again.

Other error codes

Code Main lead
502 PHP or the application service is not responding correctly. Check proxy_error_log and error_log
503 The site may be suspended. Make sure its status is Active in Websites & Domains. Otherwise, contact support
504 A task is taking too long. Look for upstream timed out in proxy_error_log

Check the result

  1. Start real-time updates again.
  2. Reload the page that failed: it should display with no new error.
  3. Test other pages, the admin area and forms.
  4. Remove debug settings and temporary files such as .htaccess.bak.

Troubleshooting

Symptom Likely cause What to do
No line appears Wrong domain selected, or the error comes from the application Check the domain and subdomain, then look for the application's log
The time does not match The log uses the server's time zone Use real-time mode to avoid confusion
Older errors have disappeared Logs are archived by rotation Look for archived files under Manage Log Files
The log fills up very quickly An error repeats on every request Fix the first error, then watch the log again
The message does not let you conclude Cause related to the server or a plan limit Contact support with the page address, the time, your IP address and the full log line

Further reading