next.js with-turbopack occasionally throws "Error during SSR rendering - timed out waiting for the Node.js process to connect" when navigating pages

with-turbopack occasionally throws "Error during SSR rendering - timed out waiting for the Node.js process to connect" when navigating pages

Open muradbu opened this issue 1 year ago • 23 comments

Verify canary release

[X] I verified that the issue exists in the latest Next.js canary release

Provide environment information

Using Windows 10 with WSL2:

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Fri Apr 2 22:23:49 UTC 2021
    Binaries:
      Node: 16.17.1
      npm: 8.15.0
      Yarn: N/A
      pnpm: 7.14.0
    Relevant packages:
      next: 13.0.0
      eslint-config-next: 13.0.0
      react: 18.2.0
      react-dom: 18.2.0

Which example does this report relate to?

with-turbopack

What browser are you using? (if relevant)

Firefox 107.0b4

How are you deploying your application? (if relevant)

No response

Describe the Bug

The new with-turbopack example occasionally throws during dev:

error - [rendering] [root of the dev server]/[CURRENT ROUTE TRYING TO RENDER]
  Error during SSR Rendering
  timed out waiting for the Node.js process to connect

Most of the time the page does end up rendering successfully and an event - updated in _xxx_ms gets logged, but on some occasions it throws the above error in the console while still rendering the page. I can still navigate to other pages, but the console stops logging events. This can happen on all pages when I navigate to them.

Sometimes the error blocks the entire page from rendering by throwing an error in the browser, although this only occurred twice:

I cannot figure out a pattern that causes this error, the pages load fine most of the time but occasionally throw this error unexpectedly.

Expected Behavior

On navigating, a page should render without errors, echoing an event to the console with the amount of time it took to update.

To Reproduce

Create a new project using the example.

pnpm create next-app --ts --example with-turbopack

Run the dev command (--turbo is included in the dev script by default in this example.)

pnpm run dev

Go to http://localhost:3000 in the browser and click the links in the sidebar to navigate to different pages. 3.a. Pay attention to the console as the error might be thrown even though the page rendered.
After some successful navigation events this error might be thrown (multiple times if you continue navigating): 4.a On some occasions the error can be thrown in the browser as well, preventing the page from rendering.

Oct 26 '22 14:10 muradbu

I have the same problem...

Oct 27 '22 03:10 zacard-orc

I am also facing this issue currently – for me, it is happening on every render.

Version: "next": "13.0.0" Command: yarn dev -- --turbo (next dev --turbo)

Oct 27 '22 09:10 juriadams

Switching from node14 to node16 fixed this for me.

using nvm

nvm use 16

Oct 27 '22 13:10 nickbuckham

I used Node 16 and it worked!

npm install -g n n

Oct 27 '22 19:10 iamanas20

Switching from node14 to node16 fixed this for me.

using nvm

nvm use 16

Weird, I'm already on 16.17.1

Oct 27 '22 22:10 muradbu

I'm having the same problem on node version: 16.15.1 Edit: Tried to upgrade to node 18 LTS but i'm still having the same problem

M1 Max chip

Oct 28 '22 06:10 notlimey

It didn't work for me on node v14, but I tried with v16.18.0, and it works well.

Oct 28 '22 10:10 webston

The same issue. v14, v16, v16.18.0 - are not working.

Turbopack failed to compile error - [rendering] [root of the dev server]/ Error during SSR Rendering timed out waiting for the Node.js process to connect

PS: SoC M1

Oct 29 '22 10:10 o2sevruk

I am getting this on every load using Windows 11, WSL2, Ubuntu 22.04, node 16 and node 18. If I run this directly on Windows 11 with node 16 it seems to work fine.

Oct 29 '22 16:10 nrowan

Same issue happens in M1 Mac as well, with Node 19

Oct 29 '22 23:10 praveenkumarsaravanan

M1 Pro, Node LTS - happening here too

Oct 30 '22 10:10 franzwilhelm

Uhm , having issue, MBP 2018, Switched node versions to 16 as well and still the same

Oct 30 '22 14:10 khervie-star

I'm having the same problem on node version: v16.15.1 and v18.12.0

Oct 30 '22 20:10 ssynowiec

I also have this problem in window 10 19044.2130 ,node v16.15.0 and there are no errors in the console, only on the page

Oct 31 '22 03:10 littleCareless

got same error using node 14.20.1, but running well using node 16.18.0 (windows 11)

Oct 31 '22 06:10 agustrinaldokurniawan

I am on v16.13.0 and getting the same error.

Oct 31 '22 14:10 RajVarsani

16.18.0 worked for windows! Does not work with M1 MAC

Nov 01 '22 12:11 YunosukeYoshino

Having the same issue. It does not work even with v16.18.0.

Nov 06 '22 12:11 nsaicharan

I am also getting the same error using trubopack, webpack ain't showing any kind of errors. node version 16.17.1

Nov 07 '22 04:11 b-meet

node: 16.13.1

It was working fine at first, but then it suddenly stopped working.

EDIT: I resolved my issue. First time using Next.JS so I'm still learning as I go. I was attempting to use CSR but also by having my page as an async function. Removing the async signature resolved my issue.