Dynamic route page is not found
Unanswered
Georgian Shepherd posted this in #help-forum
Georgian ShepherdOP
When I develop locally my dynamic pages are showing without any problems but when I deploy my app to prod dynamic pages are not found. I use app router and I use a separate application for API. I use next.js only as a frontend framework. In Vercel my framework preset is "Next.js". Do you know why my dynamic pages are not found on the deployed version?
13 Replies
Toyger
check console logs and servers logs, also provide code of this page maybe you just conditionnaly not render it
Georgian ShepherdOP
Here is the code of the page
In the console I don't have any errors. On the server side I don't have any logs at all
Toyger
what do you mean no logs at all? it should be at least some rutime logs at server.
and what about page itself if you open devtools do you have anything rendered there, maybe block in place but data not
and what about page itself if you open devtools do you have anything rendered there, maybe block in place but data not
Georgian ShepherdOP
When I open page with devtools there are code of not-found page
Request to get page
Toyger
are other pages working?
Georgian ShepherdOP
yes, all the pages are working fine. Only this dynamic page is not working and only in deployed version
Toyger
are you sure that last code is deployed, also try to restart local environment and check route again
Georgian ShepherdOP
I started my app locally not in dev mode and now I have the same error as in prod
I think the issue that I don't use next.js api but fetch data from other server in useEffect, but I don't knwo how to fix it
Toyger
no, it's not a problem.
try to make minimal route that will output static text, if it works in prod build then try to add some chunks of your current route like useeffect etc..
but I think right now problem in route itself, maybe something with filename or other thing.
try to make minimal route that will output static text, if it works in prod build then try to add some chunks of your current route like useeffect etc..
but I think right now problem in route itself, maybe something with filename or other thing.