View error logs in DirectAdmin

Error logs are essential for troubleshooting website problems. In this guide, we explain how to view error logs in DirectAdmin.

What are error logs?

Error logs are files where the server records errors that occur while running your website. They contain:

• PHP errors and warnings
• Apache web server errors
• Access problems (403, 404, 500 errors)
• Database connection issues

Viewing error logs

Via DirectAdmin

1. Log in to DirectAdmin
2. Go to Error Logs or Site Logs
3. Select the log type:
   • Error Log: Web server errors
   • Access Log: All visitors and requests
4. You'll see the last lines of the log file

Via File Manager

Logs are in /domains/example.com/logs/:

• error.log - Error messages
• access.log - Access logs

Via FTP or SSH

Download the logs via FTP to analyze them in a text editor. If you have SSH access, you can follow a log file in real time with tail -f, for example tail -f error.log. New errors then appear immediately while you test your website.

Reading error logs

Typical PHP error:

[14-Jan-2026 10:30:45] PHP Fatal error: Uncaught Error:
Call to undefined function example() in /home/user/domains/example.com/public_html/file.php:25

Means:

• Date/time: When the error occurred
• Type: Fatal error (critical)
• Message: Function doesn't exist
• Location: file.php, line 25

HTTP status codes

Common errors

PHP Fatal error

PHP Fatal error: Allowed memory size exhausted

Solution: Increase memory_limit in PHP settings.

File not found

File does not exist: /home/user/.../favicon.ico

Solution: Upload the missing file or ignore.

Permission denied

[error] [client IP] Permission denied: /path/to/file

Solution: Check CHMOD permissions (644 for files, 755 for folders). Never use 777: it is an unnecessary security risk.

Database connection error

Warning: mysqli_connect(): Access denied for user

Solution: Check the database name, username and password in your configuration file (for WordPress this is wp-config.php).

Tips for debugging

1. Check the timestamp: Recent errors are more relevant
2. Look for patterns: Same error repeatedly? Fix the cause
3. Start at bottom: Newest errors are at the bottom
4. Note the line: File and line number point to the error
5. Google the error: Many errors have been solved by others
6. Reproduce the problem: Perform the action that causes the error while you watch the log

WordPress debug mode

For more details in WordPress:

// In wp-config.php
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Logs appear in /wp-content/debug.log. Set WP_DEBUG back to false once you have found the problem.

Need help?

We're here for you! Running into issues or have questions? Our support team is happy to help you personally. Drop us a message through the ticket system - we usually respond within a few hours and love helping you find the best solution.