404: NOT_FOUND
The Vercel deployment has no file or route at this path
Seen in Vercel
The deployment exists, but nothing in its build output or routes matches the requested path.
Common causes
- A single-page app route with no rewrite to index.html.
- The wrong output directory or framework preset, so the deployment is missing files.
- A path that differs in case from the file name.
How to fix it
- For single-page apps, add a rewrite in vercel.json: {"rewrites": [{"source": "/(.*)", "destination": "/index.html"}]}
- Check the project's framework preset and output directory, then redeploy.
- Inspect the deployment's Source and Output tabs to see which files were built.
Got a different message? Paste it into the error explainer.
Related errors
- 408 Request Timeout · The client took too long to send its request
- 413 Request Entity Too Large · The request body is bigger than the server allows
- 431 Request Header Fields Too Large · The request headers are too big
- 400 Bad Request: Request Header Or Cookie Too Large · nginx rejected oversized headers or cookies
- 499 Client Closed Request · The client gave up before nginx answered
- Error 524: A timeout occurred · Your origin took longer than 100 seconds to respond
- Error 530 · Cloudflare could not reach the origin; see the 1xxx error on the page
- Error 1003: Direct IP access not allowed · A Cloudflare IP was requested without a hostname
- Error 1010: The owner of this website has banned your access based on your browser's signature · Your browser looks like a bot to the site's security settings
- Error 1015: You are being rate limited · You sent too many requests to a Cloudflare site
- Error 1020: Access denied · A Cloudflare firewall rule blocked your request
- Error 1033: Argo Tunnel error · The Cloudflare Tunnel for this hostname is not connected