Error in routes path undefined on f5 (refresh) #82901
Unanswered
TexLuciano
asked this question in
App Router
Replies: 1 comment
-
|
What an interesting issue. Is it an image request causing this? Are you able to see the initiator of the request in the dev tools? Any repo/live link we could see? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The error occurs when the Next.js application makes a request to the URL http://localhost:8083/settings/undefined, resulting in a 404 Not Found. This issue happens regardless of the route: even on simple pages like /contacts, after refreshing, the console inside the middleware logs the route as /undefined.
This indicates that some expected value (such as a dynamic route parameter or a configuration variable) is being passed as undefined in the middleware. However, the application still works normally and shows no visible errors on the screen. The problem is limited to page reloads (F5).
I am using Next.js 15 together with next-intl.

Beta Was this translation helpful? Give feedback.
All reactions