Deployment URL or Custom Domain:
Environment (local, preview, production):
Project Framework:
Build Settings:
Framework Preset:
Build Command (if not default):
Output Directory (if not default):
Install Command (if not default):
Node/Runtime Version:
Package Manager:
Relevant Packages:
Hey @mubarikalfablondi-pr. I wrote a longer post with tips and tricks for debugging 404 errors. Please give these a try and let me know if that helps.
The issue seems to be with the Framework preset. Can you set it to next.js or node.js depending upon the framework you are using. Ref: Configuring a Build
You can also add it form https://vercel.com/
→ project name → repo → settings
This error often occurs due to a configuration issue with your project. I took a look at the project settings and can see you have the framework set as ‘Other’. This uses default commands for the build and install steps such as npm run build
and npm install
depending on any lockfiles present or configurations in files such as package.json
.
The Output directory defaults to public
if it exists, or .
if not. If any of these configurations don’t match how you build and run your project locally then it can lead to Vercel serving an empty directory, so it shows a 404 error.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.