Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: connect ECONNREFUSED 127.0.0.1:62507 #50298

Closed
1 task done
ciruz opened this issue May 24, 2023 · 6 comments
Closed
1 task done

Error: connect ECONNREFUSED 127.0.0.1:62507 #50298

ciruz opened this issue May 24, 2023 · 6 comments
Labels
bug Issue was opened via the bug report template.

Comments

@ciruz
Copy link
Contributor

ciruz commented May 24, 2023

Verify canary release

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

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.12.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.4-canary.8
      eslint-config-next: 13.4.2
      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 or a replay of the bug

https://codesandbox.io/s/serene-elbakyan-nck1q7

To Reproduce

I setup a codesandbox but it looks like it is not compatible with the latest canary => https://codesandbox.io/s/serene-elbakyan-nck1q7

image

Describe the Bug

Just updated to the latest canary and now I get this error on Windows

- error Error: connect ECONNREFUSED 127.0.0.1:62746
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
  errno: -4078,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 62746
}
- error Error: connect ECONNREFUSED 127.0.0.1:62746
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
  errno: -4078,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 62746
}
- error Error: connect ECONNREFUSED 127.0.0.1:62746
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
  errno: -4078,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 62746
}
- wait compiling /favicon.ico/route (client and server)...
- event compiled successfully in 417 ms (433 modules)
- error Error: connect ECONNREFUSED 127.0.0.1:62746
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
  errno: -4078,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 62746
}

Expected Behavior

Don't throw an error.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

@ciruz ciruz added the bug Issue was opened via the bug report template. label May 24, 2023
@paulvanbrenk
Copy link

Looks like this is the same issue

#50290

seeing this too, and it's blocking me

@ciruz
Copy link
Contributor Author

ciruz commented May 24, 2023

Looks like this is the same issue

#50290

seeing this too, and it's blocking me

Hey thank you for the Issue.

Also if relevant, I use yarn and no Turbopack.

@ijjk
Copy link
Member

ijjk commented May 24, 2023

Hi, this has been updated in v13.4.4-canary.9 of Next.js, please update and give it a try!

@ciruz
Copy link
Contributor Author

ciruz commented May 25, 2023

Hey @ijjk I'm on next@13.4.4-canary.10 now and it works again, as expected. Thank you.

@hex2f
Copy link
Contributor

hex2f commented Jun 7, 2023

Getting this issue on next@13.4.5-canary.7 m1 macOS as well

@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2023

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

4 participants