4xx Client error
404 Not Found
The server can’t find the requested resource.
The URL doesn’t map to anything. Servers also return 404 to hide resources the client isn’t allowed to know about.
Common causes and fixes
- Check the path for typos, trailing slashes and letter case (Linux servers are case-sensitive).
- For APIs, check the base URL and version prefix (
/v1/vs/api/v1/). - Single-page apps need the server to fall back to
index.htmlfor client-side routes. - If a page was removed for good, 410 tells search engines to drop it faster; if it moved, redirect with 301.
Example response
HTTP/1.1 404 Not Found
Date: Thu, 22 Oct 2026 08:00:00 GMT Check a URL’s status with curl -I https://example.com, which prints the status line and headers.