Error fix
How to fix “404 Not Found”
The server has no resource for the URL you requested—often routing, a bad link, or a missing file.
Updated Apr 20, 2026
Tools that help with this
Fastest fix
Start here first. Step 1 fixes most cases—then work down the list.
- Confirm the path in the address bar and try the site home page, then navigate again.
- If you deploy a SPA, ensure the server returns index.html for client routes or use static hosting rules.
- Check server/CMS logs and route tables for the exact path.
What this means
HTTP 404 means the server understood the request but found nothing at that path. The host is reachable; the specific URL is not.
Common causes
Wrong URL or moved page
A typo, outdated bookmark, or CMS slug change can point to a path that no longer exists.
Deployment or routing
SPA fallback misconfigured, API route missing, or static export without a matching file.
Step-by-step fix
Verify URL and routing
- Confirm the path in the address bar and try the site home page, then navigate again.
- If you deploy a SPA, ensure the server returns index.html for client routes or use static hosting rules.
- Check server/CMS logs and route tables for the exact path.
Related
Also see: 404 — browse the HTTP status hub.
FAQ
- Is a 404 always a broken link?
- Often yes on public sites, but APIs may use 404 for “not found” resources by design. Check your app’s contract.
- Does 404 hurt SEO?
- Broken inbound links waste crawl budget; fix redirects for important URLs and return a helpful 404 page.
- Why do I see 404 on refresh in my SPA?
- The server may not be configured to serve the app shell for deep links—configure rewrites or hash routing.
Fix related issues
Still stuck? Try these related fixes next.
- Kubernetes CrashLoopBackOffThe container exits repeatedly—check logs, probes, and resource limits.
- Heroku H10 — app crashedThe web process exited; Heroku serves an error page. Logs show the real exception.
- Netlify — page not foundThe deploy exists but no asset matches the path—often SPA routing or a missing file in publish dir.
- Vercel — deployment not foundThe deployment URL or project alias does not exist or was removed.
- Cloudflare 525 — SSL handshake failedCloudflare could not complete TLS with your origin—cert mismatch, wrong port, or TLS version.
Edit your error
Tweak the message and run again—we'll match an existing fix or generate a new page.
Original error message
404 Not Found