Enable WordPress debug log (WP_DEBUG) and download debug.log

When WordPress shows a blank page, a 500 error, or “critical error”, the fastest way to understand the cause is to enable the WordPress debug log for a short time and capture the error message.

Important: do not keep debug mode enabled permanently on a production site. Enable it only while you collect the log, then disable it.

1) Open wp-config.php

1. Log in to Plesk (from My.GARMTECH → your hosting service → Plesk).
2. Go to Files (File Manager) or connect via FTP‑SSL.
3. Open your website’s document root (often httpdocs).
4. Find and edit wp-config.php.

2) Add debug settings

Add these lines above the line that says /* That's all, stop editing! */:

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

Save the file.

3) Reproduce the problem and download the log

1. Open the page or perform the action that triggers the error.
2. In File Manager, open /wp-content/.
3. Download debug.log (or open it to copy the latest lines).

4) Disable debugging after collecting the log

Set debug mode back to false:

define('WP_DEBUG', false);

You can keep the other lines or remove them — the key is to keep debugging disabled during normal operation.

Extra tip

If you also want to check web server / PHP logs, open your domain in Plesk and look for Logs / Log Browser.