When working with web servers like Apache, errors can sometimes be tricky to figure out. Fortunately, Apache provides detailed log files that can help you identify what’s going wrong. If you’re using XAMPP on Linux, your Apache logs are usually located in /opt/lampp/logs. In this guide, we’ll walk you through how to explore these logs using simple terminal commands.

📁 Step 1: Navigate to the Apache Logs Directory

Open your terminal and go to the logs directory:

cd /opt/lampp/logs

This is the default location where XAMPP stores Apache logs.

🔍 Step 2: Search for Error Messages

If you want to search through all log files for the word “error”, use the following command:

grep -R -i error .

What this does:

• -R: Searches recursively through all files and subfolders.
• -i: Makes the search case-insensitive (so it matches “ERROR”, “Error”, or “error”).
• .: Means search in the current directory.

This is useful for quickly spotting issues without opening each file manually.

📖 Step 3: View Log Files One Page at a Time

Sometimes you want to read through a log file without being overwhelmed by thousands of lines. Use more for that:

more access_log

Shows all incoming HTTP requests to your server.

more error_log

• Displays warnings, errors, and diagnostic information from Apache.

more ssl_request_log

• Lists all HTTPS-related requests, helpful for debugging SSL certificate issues.

Use the spacebar to scroll page-by-page and q to quit.

📡 Step 4: Monitor Logs in Real Time

If you’re actively testing your application and want to see logs as they happen, use the tail -f command:

tail -f access_log

Watch real-time HTTP requests as users interact with your site.

tail -f error_log

See errors pop up live as your server processes them.

tail -f ssl_request_log

• Monitor HTTPS activity in real-time.

This is incredibly useful when you’re making changes and want immediate feedback on how Apache is handling them.

🛠️ Common Use Cases for Apache Logs

• Website not loading? Check error_log.
• Getting a 404 or 500 error? Look at access_log and error_log.
• SSL not working? Inspect ssl_request_log.
• Debugging PHP? Many PHP errors also show up in the Apache error_log.