ECONNREFUSED when starting vanilla installation

[boncz92]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Fri Mar 17 01:52:38 EDT 2023
    Binaries:
      Node: 18.14.2
      npm: 9.6.6
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.2-canary.5
      eslint-config-next: 13.4.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue

create-next-app@latest

To Reproduce

npx create-next-app@latest
npm run dev

-Error occurs when attempting to navigate to site
-No additional packages installed

Describe the Bug

Error: connect ECONNREFUSED 127.0.0.1:35391
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 35391
}

error Error: connect ECONNREFUSED 127.0.0.1:36639
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 36639
}
Notice that the port changes everytime the server is started up. I can bring it up and down 100 times and itll likely be on a different port every time.

Every time the server is started up it results in the above error. I went did incremental package updates to pinpoint exactly when it broke. It appears that at 13.3.0 is when it first starts occuring. I have only seen one other thread with the same issue and there was no solution provided (or any answers on SO)

I do realize this is potentially a configuration issue with the server, I have attempted to turn off the firewall completely and same issue occurs. Some guidance on where to check would be appreciated. I see no errors in my nginx logging either.

Expected Behavior

Site should start as expected.

Which browser are you using? (if relevant)

Chrome/Edge/Firefox

How are you deploying your application? (if relevant)

Linux Rhel 8

[henrik-d]

Executing npm run build once before npm run dev resolves the issue for me.

[boncz92]

I tried to do what you recommended it does not help resolve the issue.

[TaylanTatli]

Latest versions give me this error. I'm stuck on 13.2.4. This is the latest working version for me.

[boncz92]

Latest versions give me this error. I'm stuck on 13.2.4. This is the latest working version for me.

Same here. I have a feeling its an issue with a external dependency that next references..... I just havent been able to nail down a fix for it. Issue does not occur on my personal computer. Think I will give the networking team a ring to see if they can see specific traffic being blocked.

Hopefully someone has some additional insight if my investigation turns up nothing.

[boncz92]

Latest versions give me this error. I'm stuck on 13.2.4. This is the latest working version for me.

Are you running this in an enterprise environment? Would assist with backing my theory if some external dep is getting blocked.

[TaylanTatli]

Are you running this in an enterprise environment? Would assist with backing my theory if some external dep is getting blocked.

Nope. I'm working on home.

[IonelLupu]

Latest versions give me this error. I'm stuck on 13.2.4. This is the latest working version for me.

Exactly the same here too. We had to downgrade to 13.2.4. I am using MacOS 13.3.1 on M1.

The weird thing is that the app works when served from Vercel

[ishields]

I'm having this same issue as well and had to downgrade. MacOs 13.3

[jwendin]

Also seeing this issue. Had to downgrade to 13.2.4, also using 13.3.1 M1 mac. Cant reproduce the issue locally but we see it when we deploy to k8s

[agusterodin]

I can't reproduce locally on my M1 Mac on Ventura 13.3.1 (22E772610a) but am getting spammed with errors (multiple times a minute) when deployed to Node 19 Alpine instance on Kubernetes. Is anybody getting errors like this?

{"log":"Error: read ECONNRESET\n at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {\n errno: -104,\n code: 'ECONNRESET',\n syscall: 'read'\n","stream":"stderr"}

{"log":"Error: socket hang up\n at connResetException (node:internal/errors:717:14)\n at Socket.socketOnEnd (node:_http_client:519:23)\n at Socket.emit (node:events:525:35)\n at endReadableNT (node:internal/streams/readable:1359:12)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {\n code: 'ECONNRESET'\n","stream":"stderr"}

I am on Next 13.4.2.

[TaylanTatli]

13.4.3 has same problem. Thinking about migrating to something else but it's a lot of work.

[muhammad-saleh]

I had this problem, I found a solution on Stackoverflow that recommends downgrading node from 18 to 16, I tried that and the problem was fixed for me (not ideal I know).

[TaylanTatli]

I had this problem, I found a solution on Stackoverflow that recommends downgrading node from 18 to 16, I tried that and the problem was fixed for me (not ideal I know).

I can confirm this works. I was using Node 20.2.0. Thanks for sharing but this's not a proper solution. 😞

[IonelLupu]

One thing to know is that creating a new NextJS app (currently at 13.4.3), the app works with no issues.

I think the problem is with the old apps. I have an app which I created with NextJS 13.0.0. I had no issues with updating the "next" package from 13.0.0, 13.1.0. etc until 13.2.4. Updating to 13.4.3 now, on the old project, gives this error.

This is my next info of the next 13.2.4 project:

 Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.2.4
      eslint-config-next: 13.1.6
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "13.2.4", newest: "13.4.4-canary.0".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

And these are the packages:

    "dependencies": {
        "@auth0/nextjs-auth0": "2.2.1",
        "@cloudflare/stream-react": "1.8.0",
        "@datadog/browser-rum": "4.32.1",
        "@growthbook/growthbook-react": "0.11.1",
        "@react-google-maps/api": "2.18.1",
        "@segment/snippet": "4.15.3",
        "@sentry/nextjs": "7.51.1",
        "@sentry/react": "7.51.1",
        "@stripe/react-stripe-js": "1.16.4",
        "@stripe/stripe-js": "1.46.0",
        "@tanstack/react-query": "4.24.4",
        "antd": "5.5.0",
        "antd-mask-input": "2.0.7",
        "cookies-next": "^2.1.1",
        "crypto-js": "4.1.1",
        "eslint": "8.33.0",
        "eslint-config-next": "13.1.6",
        "eventsource": "2.0.2",
        "lodash": "^4.17.21",
        "markdown-to-jsx": "7.1.9",
        "next": "13.2.4",
        "react": "18.2.0",
        "react-date-range": "1.4.0",
        "react-device-detect": "2.2.3",
        "react-dom": "18.2.0",
        "react-infinite-scroll-component": "6.1.0",
        "react-phone-number-input": "3.2.22",
        "react-spring": "9.7.1",
        "sharp": "0.32.1",
        "typescript": "4.9.5",
        "zustand": "^4.3.6"
    },
    "devDependencies": {
        "@commitlint/cli": "17.4.4",
        "@commitlint/config-conventional": "17.4.4",
        "@commitlint/cz-commitlint": "^17.4.4",
        "@commitlint/prompt": "17.4.4",
        "@commitlint/prompt-cli": "17.4.4",
        "@cypress/code-coverage": "3.10.0",
        "@next/bundle-analyzer": "^13.2.4",
        "@semantic-release/github": "^8.0.7",
        "@semantic-release/npm": "^9.0.2",
        "@semantic-release/release-notes-generator": "^10.0.3",
        "@types/crypto-js": "4.1.1",
        "@types/cypress": "^1.1.3",
        "@types/lodash": "^4.14.192",
        "@types/node": "18.11.19",
        "@types/react": "18.0.27",
        "@types/react-date-range": "^1.4.4",
        "@types/react-dom": "18.0.10",
        "@types/segment-analytics": "0.0.34",
        "autoprefixer": "10.4.13",
        "babel-plugin-istanbul": "6.1.1",
        "commitizen": "^4.3.0",
        "concurrently": "7.6.0",
        "conventional-changelog-atom": "^2.0.8",
        "conventional-changelog-conventionalcommits": "5.0.0",
        "cypress": "^12.11.0",
        "cypress-mailslurp": "1.6.0",
        "cypress-promise": "1.1.0",
        "date-fns": "2.29.3",
        "eslint-config-prettier": "8.6.0",
        "husky": "8.0.3",
        "lint-staged": "13.1.0",
        "openapi-typescript-codegen": "0.23.0",
        "postcss": "8.4.21",
        "prettier": "2.8.3",
        "sass": "1.57.1",
        "semantic-release": "20.1.1",
        "tailwindcss": "3.2.4",
        "typewriter": "8.1.0",
        "wait-on": "7.0.1"
    },