[auth][error] TypeError: fetch failed

[danisal]

Hi,

I'm facing an issue for which I just found the solution (?), but nevertheless, I wanted to ask for your help since this doesn't seem like a solution to me.

I'm using the latest version of next-auth (5.0.0-beta.19) with the provider Zitadel, and this is the screen I see when I try to deploy the next app on Vercel with an auth proxy also deployed on Vercel.

And the server console only tells me this:

[auth][error] TypeError: fetch failed
    at node:internal/deps/undici/undici:12502:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async getAuthorizationUrl (webpack-internal:///(rsc)/../../node_modules/next-auth/node_modules/@auth/core/lib/actions/signin/authorization-url.js:24:35)
    at async Module.signIn (webpack-internal:///(rsc)/../../node_modules/next-auth/node_modules/@auth/core/lib/actions/signin/index.js:16:56)
    at async AuthInternal (webpack-internal:///(rsc)/../../node_modules/next-auth/node_modules/@auth/core/lib/index.js:72:24)
    at async Auth (webpack-internal:///(rsc)/../../node_modules/next-auth/node_modules/@auth/core/index.js:126:34)

Using the same locally, with a local instance of the auth-proxy, everything works just fine.

By chance, I've found that disabling the NODE_TLS_REJECT_UNAUTHORIZED everything works just fine...

I don't know why this happens, but it isn't a good solution for me.

Does anyone know why this happens? Since everything is deployed on Vercel, it should work, I would say

[danisal]

For reference, let me say that this happened when I tried to log in. The process is supposed to bring the user to the Zitadel login screen, but it doesn't even reach Zitadel; this happens as soon as I click the login button.

[aspirin2d]

Same error here...

[wujibear]

I'm also experiencing this.
Not sure if there's something wrong with my config somewhere, or what this is meant to mean.

I tried setting NODE_TLS_REJECT_UNAUTHORIZED to zero, and then to false. I did that just to see if there's a similarity there for me.
Neither bypassed whatever this issue is, but I get this same error message.

[985563349]

I'm having the same problem with google authentication

[imrbrad]

Me too

[985563349]

I have solved this problem. The reason is that my nodejs can't access google services.

[danalex7212]

what did you do to give nodejs access to google services ? I am facing this issue with microsoft .

[985563349]

what did you do to give nodejs access to google services ? I am facing this issue with microsoft .

I can't access the Google service in my area, so I used the tun proxy mode.