next.js: Page crashes and "Error: Connection closed." appears
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
Binaries:
Node: 16.16.0
npm: 8.11.0
Yarn: N/A
pnpm: 8.6.2
Relevant Packages:
next: 13.4.10
eslint-config-next: 13.4.8
react: 18.2.0
react-dom: 18.2.0
typescript: 5.1.6
Next.js Config:
output: N/A
Which area(s) of Next.js are affected? (leave empty if unsure)
App Router
Link to the code that reproduces this issue or a replay of the bug
https://github.com/europython/website/
To Reproduce
Open this page a few times: https://ep2023.europython.eu/wasm
Describe the Bug
Same as #49205
Expected Behavior
No crash
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: 21
- Comments: 52 (8 by maintainers)
To follow up – our most recent deployment is also now ok, but it’s the first one to work today. Any sort of update from Vercel would be appreciated, especially since the status page never reflected this platform issue.
All of my broken versions randomly resolved a few hours ago with a redeploy… My API stopped truncating too.
Glad I spent 10 hours troubleshooting a Vercel issue
this seems to be ok now, is anyone else still experiencing this issue?
Could be a bug on the Vercel side? since local works perfectly
Vercel support is more than useless. Our PRO plan response time is more than 1 month. We still have unresolved issues that are pending from beginning of June. Really worried about the level of ****s given by vercel since releasing app dir.
This issue is NOT resolved we can still randomly see it, and it’s not the first time that our production deployment pipeline is blocked. There isn’t even a way to catch the runtime error and report this, so we can’t really be sure of the magnitude of the problem
Here is a support case that we just created 00146982
Thanks @chrisjh! Will close this issue now as a patch on the platform was rolled out.
If you’re on a paid plan, you can create a case from the dashboard. I’ll also be doing that if it’s not fixed at some point tomorrow as well
In my case when navigating using the
Linkcomponent. I do not usegenerateStaticParams- my setup is very simple actually.This is not a server issue. The RSC payload during the navigation is correct - it’s a client-side exception.
We’re still seeing this issue – no code changes or package updates to the page that’s crashing – was working fine previously, but a new deployment has been running into this error consistently.
I am not using it - I don’t think it’s related.
its not check serverside logs and do console logs in ur server then only u get output error without console logs u don’t get any error on server side
did u check your vercel logs that whats error you guys getting
We added a Vercel ticket immediately.
It got ghosted harder than my last text to my ex.
My wife got a response from Webkinz support faster than Vercel.
“Issues that require immediate attention” should not go to Vercel support unless you are on enterprise.
Hey folks, sorry to hear you ran into issues. I reached out internally and apparently there was an issue yesterday: https://www.vercel-status.com/incidents/5c0cpdhr3n4p.
In the future if you’re running into issues that require immediate attention please reach out to Vercel support, I understand that you ended up here in this case but GitHub issues on the Next.js repository are not monitored 24/7 (i.e. most of our team working on Next.js is in Europe).
Guidance on the vercel-status link is to redeploy the application, can you try that if you’re still running into issues?
Build seems to be working fine again. Was breaking today the whole day. Tried a new deploy now and looks fine will keep an eye open tho…
I am having the same issue, reverting is not seeming to work, serverActions are enabled and I’m using the app router. All new builds are having this issue.
I am getting data with a server function with await and it’s larger data in both cases of failure. When it’s smaller data it does not occur. My API is also getting truncated after around 64kbs and that never happened before.
Maybe it’s some issue with nextjs serverless function response limits? it’s a larger response that gets the “Error: Connection closed.” every time. Local is totally fine
Yes, the reverting didn’t actually work 😦 I checked an old deploy and that still works
Same here, it started today. Old builds are still running fine. And in our case it only happens on routes with node.js runtime.
cc @leerob wonder if this is a known issue in Vercel?
this problem occurs randomly in my application, but more systematically as my page size grow. for example, when i want to increase the number of rows displayed in a table, i can go up to a certain number (with random crashes), but after a certain point nothing works.
I also think this has something to do with Vercel.
Nope not using it.
I am hitting the same issue. I would love to put together a reproduction, but it only happens in production so it’ll take me a bit.
In my case - reverting to 13.4.8/13.4.7 does not solve the issue
Having the same issue on Next 13.4.10. It does not happen when my app is run locally. Only when it is deployed.