How to Fix 404 Not Found Nginx Error – Causes & Solutions

The 404 Not Found Nginx error occurs when the web server fails to locate the requested resource.

A 404 Not Found response is an HTTP status code (404) indicating that the server could not find the requested file, page, or directory.

Nginx is an open-source, high-performance web server, reverse proxy and load balancer commonly used for handling HTTP, HTTPS, and TCP requests.

It serves as a bridge between client requests and backend applications.

What Does 404 Not Found Nginx Mean?

A 404 error in Nginx usually results from misconfigured server settings, missing files, incorrect URL paths, or broken routing rules.

The issue can occur due to improper directives in the Nginx configuration file (nginx.conf), outdated cached data, file permission restrictions, or broken symbolic links.

This error may also appear if the requested resource has been deleted, moved, or renamed without updating the server configuration.

In some cases, proxy settings, PHP misconfigurations, or content management system (CMS) errors can also lead to Nginx returning a 404 response.

Identifying the cause and implementing the correct fix is essential for restoring website functionality and ensuring proper URL resolution.

Common Causes of 404 Not Found in Nginx

• Incorrect Nginx Configuration – Missing or misconfigured location blocks in nginx.conf.
• Missing Files or Directories – The requested resource does not exist in the document root.
• Incorrect Root Path – The root directive in the Nginx configuration points to the wrong directory.
• Permissions Issues – Nginx lacks read access to the requested files.
• Broken Symbolic Links – Symlinks pointing to non-existent or inaccessible files.
• Cache Issues – Old cached data causing conflicts.

How to Fix 404 Not Found Nginx?

1. Verify the Requested URL

Check whether the requested file or page exists. Use:

ls -lah /var/www/html/

Ensure the file path matches the request.

2. Check Nginx Configuration

Open the configuration file:

sudo nano /etc/nginx/sites-available/default

Look for the server block and validate the location directive:

server {
     listen 80;
     server_name example.com;
     root /var/www/html;
     location / {
          index index.html index.php;
     }
     location /static/ {
          root /var/www/html/static;
     }
}

If an alias is used, ensure it is correctly set:

location /images/ {
     alias /var/www/html/uploads/;
}

Restart Nginx to apply changes:

sudo systemctl restart nginx

3. Ensure File and Directory Permissions

Set proper ownership and permissions:

sudo chown -R www-data:www-data /var/www/html
sudo chmod -R 755 /var/www/html

Check if Nginx has access to the files:

sudo -u www-data ls -lah /var/www/html/

4. Verify the Root Path

Check if the root directive matches the actual file location:

grep -R "root" /etc/nginx/sites-available/

If incorrect, update it and reload Nginx:

sudo systemctl reload nginx

5. Check Nginx Error Logs

Analyze logs for detailed error messages:

sudo tail -f /var/log/nginx/error.log

Identify and fix the cause of missing resources.

6. Clear Browser and Server Cache

Remove old cache files:

sudo rm -rf /var/cache/nginx/*

Restart Nginx:

Clear browser cache and reload the page.

7. Fix Broken Symbolic Links

Check for broken links:

ls -l /var/www/html/

If a symlink is broken, recreate it:

ln -s /actual/path/to/file /var/www/html/symlink

8. Reinstall or Restart Nginx

If the issue persists, reinstall Nginx:

sudo apt-get remove nginx -y
sudo apt-get install nginx -y

Or restart the service:

sudo systemctl restart nginx

9. Fixing 404 Not Found Nginx on Android

If 404 Not Found appears on an Android device:

• Clear browser cache.
• Check the network connection.
• Use a different browser.
• Ensure the website is not blocked by a firewall or ISP.

The 404 Not Found Nginx error is often caused by misconfigured settings, missing files, or permission issues. The issue can be resolved efficiently by checking server configurations, file paths, logs, and permissions.

Check If the Error Is Resolved Using a URL Status Checker

After making the necessary fixes, verify whether the 404 Not Found Nginx error is resolved by testing the URL’s HTTP status.

Use a reliable URL status checker tool to confirm if the webpage is accessible and return the correct HTTP response.

Optimizo provides a URL status checker tool where anyone can check their website’s response codes, identify 404 errors, and analyze HTTP status codes in real time.

This tool helps ensure your site is properly configured and accessible to visitors. Simply enter your URL and check whether your page loads correctly.