What causes "HTTP 404 Not Found"?

Typo in the URL path API route not registered or has a different path File was deleted or moved on the server Trailing slash mismatch (e.g., /api/users vs /api/users/) Case sensitivity issue on Linux servers

HTTP Error2 Fixes Available

404 Not Found

HTTP 404 Not Found

What does this error mean?

A 404 means the server could not find the requested resource. The URL may be wrong, the resource may have been deleted, or the route may not be configured correctly.

Common Causes

Typo in the URL path
API route not registered or has a different path
File was deleted or moved on the server
Trailing slash mismatch (e.g., /api/users vs /api/users/)
Case sensitivity issue on Linux servers

How to Fix It (2 Solutions)

Double-check the URL

Use our URL Parser to break down and inspect every part of the URL you are requesting.

Check your router configuration

Verify the route is registered in your framework (Express, Next.js, etc.).

Code

// Express — make sure the route exists
app.get('/api/users', (req, res) => { ... });

// Next.js — check the file exists at
// app/api/users/route.ts  OR  pages/api/users.ts

Fix this error faster with our free tool

URL Parser

Open URL Parser

Related Errors

HTTP

403 Forbidden — Access Denied

View fix

HTTP

500 Internal Server Error

View fix

HTTP

401 Unauthorized — Authentication Required

View fix

Browse all error fixes