Fix Apache 500 Internal Server Error on Linux

Symptoms

When accessing a website hosted on an Apache server running Linux, users see a generic '500 Internal Server Error' page. The browser may display a blank page or an error message like 'Internal Server Error'. The error occurs intermittently or consistently, affecting all or specific pages. Server response time may be normal, but the HTTP status code is 500.

Root Causes

• .htaccess file misconfiguration: Syntax errors, incorrect directives, or conflicts with server modules (e.g., mod_rewrite).
• PHP errors: Fatal PHP errors, memory limit exhaustion, or script timeouts.
• File permissions: Incorrect ownership or permissions on web directories or files, preventing Apache from reading or executing them.
• Server module issues: Missing or misconfigured Apache modules (e.g., mod_rewrite, mod_proxy).
• Configuration syntax errors: Errors in Apache configuration files (httpd.conf, sites-available).
• Resource limits: Exhausted server resources like disk space, memory, or inodes.

Step-by-Step Fix

1. Check Apache Error Logs: Run tail -100 /var/log/apache2/error.log (or /var/log/httpd/error_log on RHEL/CentOS). Look for recent entries with '500' or 'Internal Server Error'. The log often pinpoints the exact issue.
2. Verify .htaccess File: Temporarily rename .htaccess to .htaccess_backup using mv .htaccess .htaccess_backup. If the error disappears, the .htaccess file is the cause. Check its syntax with apachectl -S or httpd -S after re-enabling.
3. Check PHP Error Logs: For PHP-based sites, view /var/log/php-error.log or enable error display in php.ini (display_errors = On) temporarily. Common issues: syntax errors, undefined functions, or memory limits.
4. Test Apache Configuration Syntax: Run apachectl configtest or httpd -t. Fix any reported syntax errors in configuration files.
5. Review File Permissions: Ensure web files are readable by Apache user (www-data or apache). Use chmod 755 for directories and chmod 644 for files. Check ownership with chown -R www-data:www-data /var/www/html.
6. Check Disk Space and Inodes: Run df -h and df -i. Free up space if partitions are full.
7. Disable Modules One by One: If error persists, disable recently added Apache modules using a2dismod module_name and restart Apache.
8. Restart Apache: After changes, restart service: systemctl restart apache2 or service httpd restart.

Alternative Fixes

• Increase PHP memory limit: Edit php.ini (memory_limit = 256M) and restart Apache.
• Check for infinite loops: In .htaccess, ensure RewriteRule conditions don't cause loops.
• Disable mod_security: If installed, try disabling it temporarily to rule out false positives.
• Use strace: For advanced debugging, run strace -p [apache PID] to trace system calls.

Prevention

• Regularly review Apache error logs to catch issues early.
• Test .htaccess changes in a staging environment before deploying.
• Set up monitoring to alert on 500 errors.
• Keep Apache and PHP updated to avoid known bugs.
• Use version control for configuration files to track changes.
• Implement proper file permissions and ownership from the start.

By following these steps, you can effectively diagnose and resolve Apache 500 Internal Server Errors on Linux, ensuring your web server runs smoothly.