Next.js Discord

Discord Forum

TypeError: Response.clone: Body has already been consumed.

Answered
Wesley Janse posted this in #help-forum
Open in Discord
Avatar
Wesley JanseOP
On Vercel we are sometimes getting "TypeError: Response.clone: Body has already been consumed." when loading RSC's. resulting in it rendering the error.tsx route.

This is the full error:
TypeError: Response.clone: Body has already been consumed.
    at webidl.errors.exception (node:internal/deps/undici/undici:3384:14)
    at _Response.clone (node:internal/deps/undici/undici:8883:31)
    at /var/task/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:181152 {
  digest: '1056355277'
}


I can't find anything online, besides that it has something to do with PPR, which we do not use.

Can anyone send me in the correct direction?
Answered by Wesley Janse
Error goes away when downgrading to node 18. as also stated in this github post. Issue has already been fixed for next 15 canary but has not been backported to next 14.

https://github.com/vercel/next.js/discussions/69635
View full answer

1 Reply

Avatar
Wesley JanseOP
Error goes away when downgrading to node 18. as also stated in this github post. Issue has already been fixed for next 15 canary but has not been backported to next 14.

https://github.com/vercel/next.js/discussions/69635
Answer