next.js: Production Fatal Error
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
at validateURL (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/app-render/validate-url.js:24:19)
at renderToHTMLOrFlight (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/app-render/app-render.js:102:51)
at NextNodeServer.renderHTMLImpl (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/next-server.js:694:20)
at /app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/next-server.js:685:105
at NextTracerImpl.trace (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/lib/trace/tracer.js:90:20)
at NextNodeServer.renderHTML (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/next-server.js:685:41)
at doRender (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/base-server.js:1059:37)
at cacheEntry.responseCache.get.incrementalCache.incrementalCache (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/base-server.js:1197:34)
at /app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/response-cache/index.js:99:42
at ResponseCache.get (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/response-cache/index.js:149:11)
Error: Invalid request URL
at validateURL (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/app-render/validate-url.js:24:19)
at renderToHTMLOrFlight (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/app-render/app-render.js:102:51)
at NextNodeServer.renderHTMLImpl (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/next-server.js:694:20)
at /app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/next-server.js:685:105
at NextTracerImpl.trace (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/lib/trace/tracer.js:90:20)
at NextNodeServer.renderHTML (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/next-server.js:685:41)
at doRender (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/base-server.js:1059:37)
at cacheEntry.responseCache.get.incrementalCache.incrementalCache (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/base-server.js:1197:34)
at /app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/response-cache/index.js:99:42
at ResponseCache.get (/app/node_modules/.pnpm/next@13.4.10-canary.3_@babel+core@7.22.5_react-dom@18.2.0_react@18.2.0_sass@1.63.6/node_modules/next/dist/server/response-cache/index.js:149:11)
Which area(s) of Next.js are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue or a replay of the bug
no response
To Reproduce
Just update to latest canary version you have broken this really badly
Describe the Bug
500 server error
Expected Behavior
no server error
Which browser are you using? (if relevant)
no response
How are you deploying your application? (if relevant)
no response
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 2
- Comments: 30 (8 by maintainers)
This particular code does work as expected as of
Node v18.17.0
which is released 2 days ago.v20.5.0
which will be released today/tomorrow (ref: https://github.com/nodejs/node/releases/tag/v20.5.0), will also fix this in version 20.Great! Sounds like its fixed upstream. Can we close this issue?
same issue here:
node: v20.4.0 next: 13.4.10
also only happens in production.
any fixes / workarounds yet?