Updated: 13 November 2026 · Applies to: DirectAdmin, WordPress on Apache or nginx

Match the symptom to the right log first, or you end up reading the wrong file. A missing page shows in the web server's access log, a crash or a blank white screen shows in the PHP error log, and a site that will not load at all is usually a service that is not running. For the full list of log paths on a DirectAdmin server, see DirectAdmin Locations of Logs; this article is about which one to open for a WordPress problem and what to look for in it.

"Page not found" or a broken link

This is a 404, not an error: WordPress or the web server answered normally and said the page does not exist. Check the access log, not the error log.

tail -20 /var/log/httpd/domains/example.com.log

Look for the request with a 404 status code. A genuinely missing page never writes anything to the error log. Tested directly: a request for a non-existent URL on Apache logs only to the access log with status 404 and writes nothing to the error log at all.

White screen, "Error establishing a database connection", or a 500 error

Check the PHP error log, since this is almost always a PHP fatal error or a database problem, not a web server configuration issue.

tail -40 /var/log/httpd/domains/example.com.error.log

If WordPress's own debug logging is off, turn it on temporarily for a clearer message (never leave this on for a live site, since it exposes file paths):

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Add those three lines to wp-config.php above the "That's all, stop editing!" line, reload the broken page once, then check:

tail -40 /var/www/html/example.com/wp-content/debug.log

According to WordPress's own documentation, this writes every PHP notice, warning and fatal error WordPress sees to that one file, with the exact file and line number that failed, which is usually enough to point at the broken plugin or theme.

The site does not load at all (connection refused, not a 404)

This is not a WordPress problem. Check whether the web server is actually running:

systemctl status httpd

If it is stopped, start it and then read /var/log/httpd/error_log (the server-wide log, not the per-domain one) for why it stopped, for example a configuration syntax error from a recently edited .htaccess file.

Emails from the site (password resets, order notifications) never arrive

This is a mail delivery problem, not a web or PHP problem. Check the mail log instead:

tail -20 /var/log/exim/mainlog

Look for the recipient address near the time the email should have sent, and whether the line ends in a delivery or a bounce.

The site is slow, not broken

Neither the access log nor the error log shows timing. Check the database's own slow query log if MySQL or MariaDB is installed locally, or ask your host to check it if the database is on a separate server.

Official documentation: Debugging in WordPress.

Related services

Server management

on-demand administration, hardening, migrations and monitoring.

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Was this answer helpful?

Still stuck? Open a ticket