rkang427
(Rkang427)
April 28, 2025, 6:19pm
1
Hello, I’d really like some help. I’ve deployed a serverless DB using Neon and backend using Render and I’ve gotten it to work with those links hardcoded in my local environment. I also realigned my directory to work with Next.js based on a previous answer.
Would anyone know why I’m still getting a 404: NOT FOUND error?
My most recent changes have been pushed below and should work when running npm run build and npm run start.
system
(system)
April 28, 2025, 6:19pm
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 .
It looks like you’re overriding the builds configuration in your vercel.json
rkang427
(Rkang427)
April 29, 2025, 1:37pm
4
Thank you for your reply Jacob - how can I fix this issue?
pawlean
(Pauline P. Narvas)
April 29, 2025, 1:38pm
5
@rkang427 Could you try deleting the builds configuration from your vercel.json file?
rkang427
(Rkang427)
April 29, 2025, 1:42pm
6
Thank you for your reply Pauline - looks like it works when I changed the src to package.json thank you!!
1 Like
pawlean
(Pauline P. Narvas)
April 29, 2025, 1:48pm
7
I’m glad we got there in the end!
system
(system)
Closed
May 6, 2025, 1:49pm
8
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.