How to Fix 500 Internal Server Error

In this tutorial, you'll learn about How to Fix 500 Internal Server Error. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

The Problem

Your web application returns:

500 Internal Server Error
The server encountered an internal error and was unable to complete your request.

Or:

HTTP/1.1 500 Internal Server Error

A 500 error means the server-side code threw an unhandled exception or the server configuration is broken. The browser does not show details for security reasons, so you need to check the server logs.

Quick Fix

Step 1: Check the server error logs

Nginx + PHP-FPM:

sudo tail -100 /var/log/nginx/error.log
sudo tail -100 /var/log/php-fpm/error.log

Apache:

sudo tail -100 /var/log/apache2/error.log

Node.js/Express:

Look at the terminal output or application logs:

pm2 logs my-app
# or
journalctl -u my-app -n 50 --no-pager

Step 2: Enable error display temporarily

PHP: Add to your script temporarily:

ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(E_ALL);

Python Flask: Enable debug mode:

export FLASK_ENV=development
flask run --debug

Step 3: Check file permissions

A common cause of 500 errors is incorrect permissions on files or directories:

# Check web root permissions
ls -la /var/www/html/

# Fix if needed
sudo chown -R www-data:www-data /var/www/html/
sudo find /var/www/html/ -type f -exec chmod 644 {} \;
sudo find /var/www/html/ -type d -exec chmod 755 {} \;

Step 4: Restart the web server

sudo systemctl restart nginx
# or
sudo systemctl restart apache2

Alternative Solutions

Check for syntax errors in configuration files:

sudo nginx -t
sudo apachectl configtest

Prevention

• Always set up proper error logging before deploying.
• Display generic error pages to users while logging detailed errors.
• Test configuration changes with syntax check commands.
• Use version control for configuration files.