TypeError: fetch failed v18.13.0

[eucciferri]

Version

v18.13.0

Platform

Darwin Kernel Version 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000 arm64

Subsystem

No response

What steps will reproduce the bug?

Request with private production credentials to back-end

How often does it reproduce? Is there a required condition?

When you try to fetch to an external url (different from front-end)

What is the expected behavior?

Successful response (ok)

What do you see instead?

https://next-auth.js.org/errors#oauth_callback_handler_error fetch failed {
  message: 'fetch failed',
  stack: 'TypeError: fetch failed\n' +
    '    at Object.fetch (node:internal/deps/undici/undici:14062:11)\n' +
    '    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n' +
    '    at async Object.jwt (webpack-internal:///(api)/./pages/api/auth/[...nextauth].ts:116:37)\n' +

Additional information

There was another issue like this, but in other versions of node:
nodejs/undici#1248

(If I change localhost to 127.0.0.1 there's no problem)

[martinssonj]

I have the same problem when trying to move from node 16 to 18. If it is possible to set autoSelectFamily to true for fetch calls it maybe would fix this problem. https://nodejs.org/docs/latest-v18.x/api/net.html#socketconnectoptions-connectlistener

[eucciferri]

Hi @martinssonj!

I was able to solve the problem with a comment that a person made here nodejs/undici#1248 (comment)

I commented out the following line in my /etc/hosts file and it worked for me, but I think this deserves a major revision to solve the root problem.

# ::1 localhost

I think this problem comes from v17 because this comment nodejs/undici#1248 (comment)

[rei-iku]

Hi @martinssonj!

I was able to solve the problem with a comment that a person made here nodejs/undici#1248 (comment)

I commented out the following line in my /etc/hosts file and it worked for me, but I think this deserves a major revision to solve the root problem.

# ::1 localhost

I think this problem comes from v17 because this comment nodejs/undici#1248 (comment)

Thanks a lot for this, worked for me

[xfkrahmad]

Hi @martinssonj!
I was able to solve the problem with a comment that a person made here nodejs/undici#1248 (comment)
I commented out the following line in my /etc/hosts file and it worked for me, but I think this deserves a major revision to solve the root problem.

# ::1 localhost

I think this problem comes from v17 because this comment nodejs/undici#1248 (comment)

Thanks a lot for this, worked for me

can you show me your hosts file bro? i cannot fix this problem

[rei-iku]

Yes, final result is this, located at /etc/hosts:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1	localhost
255.255.255.255	broadcasthost
#::1             localhost

[avallete]

I don't know if that'll be very useful but the issue happened in our stack as well after upgrading to Node 18 LTS here is the stacktrace we get:

      return new TRPCClientError(result.message, __vite_ssr_import_0__.default(__vite_ssr_import_0__.default({}, opts), {}, {
             ^

TRPCClientError: fetch failed
    at Function.from (<project-dir-location>/node_modules/@trpc/client/dist/TRPCClientError-09b8a26b.esm.js:67:14)
    at <project-dir-location>/node_modules/@trpc/client/links/httpLink/dist/trpc-client-links-httpLink.esm.js:57:34 {
  originalError: TypeError: fetch failed
      at Object.fetch (node:internal/deps/undici/undici:11457:11) {
    cause: Error: read ECONNRESET
        at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
      errno: -54,
      code: 'ECONNRESET',
      syscall: 'read'
    }
  },
  shape: undefined,
  data: undefined,
  isDone: false,
  [cause]: TypeError: fetch failed
      at Object.fetch (node:internal/deps/undici/undici:11457:11) {
    cause: Error: read ECONNRESET
        at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
      errno: -54,
      code: 'ECONNRESET',
      syscall: 'read'
    }
  }
}

Node.js v18.16.0
Exited with 1

I've tried the following things:

1. Commenting out the "::1 localhost" in my /etc/hosts file.
2. Turning every mention to "localhost" into "127.0.0.1" in my code.

None of those fixed the issue.

[Lpmvb]

same with me

[gmoqa]

Hi @martinssonj!

I was able to solve the problem with a comment that a person made here nodejs/undici#1248 (comment)

I commented out the following line in my /etc/hosts file and it worked for me, but I think this deserves a major revision to solve the root problem.

# ::1 localhost

I think this problem comes from v17 because this comment nodejs/undici#1248 (comment)

worked for me