system
(system)
November 21, 2024, 2:31am
2
There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.
Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found.
There are many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it.
Debugging Tips
Check the error code
If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…
A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0 .
@rekflow It looks like the “Configuration Settings in the current Production deployment differ from your current Project Settings.” Can you please check your configuration settings and Vercel.json and check if both matches.
rekflow
(Rekflow)
November 21, 2024, 5:36pm
4
Thank you @neerajkumar61 . I’ve tried troubleshooting how to fix this discrepancy but I’ve come up empty. Here is what is in my vercel.json file
{
"version": 2,
"builds": [
{
"src": "frontend/package.json",
"use": "@vercel/next"
},
{
"src": "api/index.py",
"use": "@vercel/python",
"config": {
"maxLambdaSize": "15mb",
"runtime": "Python 3.12.4"
}
}
],
"routes": [
{
"src": "/api/(.*)",
"dest": "/api/index.py"
}
],
"rewrites": [
{
"source": "/api/:path*",
"destination": "/api/index.py"
},
{
"source": "/(.*)",
"destination": "/frontend/$1"
}
]
}
system
(system)
Closed
December 21, 2024, 5:37pm
5
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.