404
Not Found
The server cannot find the requested resource. The URL does not match any known route or file on the server. This is the most common HTTP error users encounter.
What does HTTP 404 mean?
The server cannot find the requested resource. The URL does not match any known route or file on the server. This is the most common HTTP error users encounter.
Common causes
- 1
The URL is misspelled or contains a typo. A single wrong character in the path makes the resource unreachable.
- 2
The resource was deleted or moved without setting up a redirect. Old bookmarks and external links now point to nothing.
- 3
The server-side routing is misconfigured — the route exists in code but the web server or reverse proxy does not forward the request correctly.
How to fix it
- 1
Verify the URL is correct. Check for typos, case sensitivity (URLs are case-sensitive on most servers), and trailing slashes.
- 2
If the resource was moved, set up a 301 redirect from the old URL to the new one. This preserves SEO value and fixes broken links.
- 3
Check your server configuration — nginx/Apache location blocks, reverse proxy routes, or framework routing rules may not match the URL pattern.
Monitor for HTTP 404 errors
A critical page returning 404 means lost traffic and revenue. Uptrack monitors your key URLs and alerts you within 30 seconds if any start returning 404, so you can fix broken routes immediately.
Catch HTTP errors before your users do
20 monitors free — 10 at 30s, 10 at 1min. No credit card required.
Start Monitoring Free