To check a WordPress error log, enable logging in wp-config.php, reproduce the problem, then open wp-content/debug.log. Keep errors hidden from visitors by setting WP_DEBUG_DISPLAY to false, and turn debugging off and remove the log when you finish.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Before you start
This is a general WordPress file-based logging procedure. The exact File Manager or dashboard labels depend on your hosting provider, and managed WordPress hosts may restrict file access or offer different debugging settings. If the instructions do not match your host’s dashboard, check its documentation; hosting.com’s WordPress debugging guide covers host-specific debugging.
As an Amazon Associate I earn from qualifying purchases.
You will need access to the site’s files through your hosting account’s File Manager or FTP, and permission to edit wp-config.php. The file is usually in the site root, often a directory named public_html. Make sure you are working in the directory for the WordPress site that is experiencing the problem.
Enable WordPress error logging
-
Open your hosting account’s File Manager or connect to the site with FTP. Navigate to the WordPress installation’s root directory and locate
wp-config.php. -
Open
wp-config.phpfor editing. Ifdefine( 'WP_DEBUG', false );is already present, change its value totrue; do not add a second definition for the same setting. -
Add the logging settings below above the line that says
That's all, stop editing!:Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false );WP_DEBUGenables WordPress debugging,WP_DEBUG_LOGdirects logged messages to a file, andWP_DEBUG_DISPLAYset tofalseprevents errors from being printed to visitors. The placement and settings are described by WPBookster, WPBeginner and wp-staging. -
Save the edited file. Check that the three definitions appear only once and are above the stop-editing line.
Reproduce the error and open the log
WordPress creates debug.log only after something is logged, so the file may not appear immediately after enabling the settings. Revisit the page or perform the action that triggers the problem, then refresh the file listing.
In File Manager, open the installation’s wp-content directory and view or edit debug.log. With FTP, navigate to /wp-content/ and download the file to read it in a text editor. The log’s path is wp-content/debug.log; the file-opening steps are also covered by WPBookster and this Prostack cPanel guide.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
If you are investigating a blank screen or an HTTP 500 error, the error may not be visible on the page. Check the log after reproducing the failure instead of relying on an on-screen message.
If debug.log does not appear
-
Trigger the issue again. The log file appears only after WordPress has something to write. Reload the affected page or repeat the action, then refresh the
wp-contentdirectory in File Manager. -
Check whether
wp-contentis writable. If WordPress cannot write to that directory, it cannot create the log there. -
Recheck the configuration. Confirm the definitions are in the site’s active
wp-config.php, above the stop-editing line, and that you changed an existingWP_DEBUGdefinition rather than adding a duplicate.What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Check your host’s method. A managed WordPress provider may restrict access to files or use its own debugging settings. Use the host’s documentation if the file-based procedure does not match the tools available to you.
These file-creation and write-access checks are identified in WPBookster’s WordPress debug-log guide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.After you find the error
Use the log to investigate the problem, then disable debugging when you are finished. In wp-config.php, set WP_DEBUG and WP_DEBUG_LOG back to false. Delete wp-content/debug.log after fixing the issue: it can grow large and may reveal file paths. The cleanup steps are documented by WPBookster.
Do not leave debugging enabled as a permanent setting on a live site. Keeping WP_DEBUG_DISPLAY set to false prevents logged errors from being printed to visitors while you investigate, but it does not remove the need to turn logging off and remove the file afterward.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
