Turbopack Error: failed to receive message

[Temwani-Nyondo]

Turbopack version: da605e0c
Next.js version: 0.0.0

Error message:

failed to receive message

Caused by:
- reading packet length
- An existing connection was forcibly closed by the remote host. (os error 10054)

Debug info:
- Execution of get_written_endpoint_with_issues_operation failed
- Execution of PlainIssue::from_issue failed
- Execution of PlainSource::from_source failed
- Execution of <WebpackLoadersProcessedAsset as Asset>::content failed
- Execution of WebpackLoadersProcessedAsset::process failed
- Execution of evaluate_webpack_loader failed
- failed to receive message
- reading packet length
- An existing connection was forcibly closed by the remote host. (os error 10054)

[JNEWSP]

This error usually means the connection between Turbopack and its worker process was interrupted:

failed to receive message
An existing connection was forcibly closed by the remote host. (os error 10054)

On Windows this typically happens when a process, firewall, VPN, or antivirus kills the connection while Turbopack is reading data.

A few things you can try:

1. Restart the dev server completely

   • Stop all next dev / Turbopack processes.
   • Start it again from the project root:

   npm run dev -- --turbo

   (or yarn dev --turbo / pnpm dev --turbo).

2. Check VPN / proxy / firewall / antivirus

   • If you’re on a corporate network, behind a proxy, or using a VPN, try disabling it temporarily or switching to a normal network.
   • Add your project folder and Node.js to the allow‑list / exceptions in your antivirus or Windows Defender.

3. Make sure the project is on a local disk

   • If the project is on a network share, WSL, Docker volume, or synced folder (OneDrive/Dropbox), try moving it to a local path like:
     • C:\Users\<your-user>\projects\my-app (Windows)
     • /Users/<user>/projects/my-app or /home/<user>/projects/my-app (macOS/Linux).

4. Clear caches in case a previous crash left things in a bad state

   macOS / Linux:

   rm -rf .next .turbo
   npm install
   npm run dev -- --turbo

   Windows (PowerShell):

   Remove-Item -Recurse -Force .next, .turbo
   npm install
   npm run dev -- --turbo

5. If it still happens, could you share more details?

   • OS and version
   • Node.js version
   • Whether you’re running inside Docker/WSL/remote dev container
   • Any VPN/proxy/firewall in use
   • Full log around the first place where os error 10054 appears

That will make it easier to see if this is a network/environment issue or a Turbopack bug.

[Temwani-Nyondo]

Thanks, I had to kill all sessions and restart dev server.

[nextjs-bot]

This discussion appears to be a duplicate of #83187.

Please follow the discussion there: #83187

---

This comment was added automatically by discussion consolidation tool. If you believe this is in error, feel free to re-open the discussion.

[nextjs-bot]

This discussion appears to be a duplicate of #90859.

Please follow the discussion there: #90859

---

This comment was added automatically by discussion consolidation tool. If you believe this is in error, feel free to re-open the discussion.