next.js 14.2.1 gives 404 on /auth/signin about next-auth HOT 15 OPEN

@adriangalilea Did you find it out any workaround?

Just staying on next 14.1.4 until this is solved.

from next-auth.

You folks are amazing ❤️

Was having the same issues of 404s on next 14.2.2, downgrading to 14.1.4 fixed it. If only folks outside of tech understood the value of open-source, the world would be a much better place.

from next-auth.

I have a similar problem. When I log in, no redirect is performed. The url remains on /sign-in. If I then do a reload, I am redirected correctly. If I then log out, it does not redirect to the /sign-in page, but remains on the last page. With a downgrade to 14.1.4 this problem does not exist.

P.S. I use [email protected]

from next-auth.

Hmm although, I just upgraded a project of mine that was having the issue as well to [email protected] and it seems to work now.

Can anyoen else confirm that it may be fixed with [email protected]+? 🙏

from next-auth.

I encountered a 404 error when clicking the "Sign In" button after deploying the NextAuth.js example to Vercel.

Here's a breakdown of the issue:

Steps to Reproduce:

• Clone the NextAuth.js example repository.
• Deploy the project to Vercel.
• Attempt to sign in using the provided button.

Expected Behavior:

The user should be redirected to the appropriate authentication flow.

Actual Behavior:

A 404 error page is displayed.

Workaround:

Downgrading Next.js to version 14.1.4 seems to resolve the issue.

from next-auth.

When I tried following, it works with NextJs 14.2.1

Example Next14.2.1

from next-auth.

@patelvivekdev tried your suggestion and it does give me 404

from next-auth.

@patelvivekdev tried your suggestion and it does give me 404

@adriangalilea Did you find it out any workaround?

P.S. I am using [email protected]

from next-auth.

I'm facing a similar issue. Works by downgrading to next 14.1.4. I'm using next-auth@^4.24.7 .

from next-auth.

Same problem in Kubernetes
"next": "14.1.4" "next-auth": "^4.24.7"

 Next.js 14.1.4
- Local:        http://localhost:3000
- Network:      http://0.0.0.0:3000

[next-auth][error][SIGNIN_OAUTH_ERROR]
https://next-auth.js.org/errors#signin_oauth_error only valid absolute URLs can be requested {
error: {
message: 'only valid absolute URLs can be requested',
stack: 'TypeError: only valid absolute URLs can be requested\n' +
'    at e.exports (/app/.next/server/chunks/638.js:39:36528)\n' +
'    at _.discover (/app/.next/server/chunks/638.js:39:42111)\n' +
'    at o (/app/.next/server/chunks/638.js:6:129314)\n' +
'    at s (/app/.next/server/chunks/638.js:6:121669)\n' +
'    at Object.s (/app/.next/server/chunks/638.js:30:8642)\n' +
'    at _ (/app/.next/server/chunks/638.js:6:107014)\n' +
'    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n' +
'    at async a (/app/.next/server/chunks/638.js:30:18310)\n' +
'    at async e.length.t (/app/.next/server/chunks/638.js:30:19720)\n' +
'    at async /app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:42484',
name: 'TypeError'
},
providerId: 'keycloak',
message: 'only valid absolute URLs can be requested'
}

from next-auth.

Yeah there seems to be an issue with [email protected]+, we're aware and are looking into it 👍

from next-auth.

Hmm although, I just upgraded a project of mine that was having the issue as well to [email protected] and it seems to work now.

Can anyoen else confirm that it may be fixed with [email protected]+? 🙏

Works on localhost but not on prod for me, not sure why.

package.json

    "next": "^14.2.3",
    "next-auth": "^5.0.0-beta.17",

And I can't see any error on logs.

repo

error is live on e-id.to, I may revert to 14.1.4 tomorrow, but in the meantime you can see the error is there still.

from next-auth.

Hmm embora, eu apenas atualizei um projeto meu que estava tendo o problema também e parece funcionar agora.[email protected]

Qualquer outra pessoa pode confirmar que pode ser corrigido com ? 🙏[email protected]+

@ndom91 That worked. But I had to reset the Nginx buffers as well.

from next-auth.

I have a similar problem. When I log in, no redirect is performed. The url remains on /sign-in. If I then do a reload, I am redirected correctly. If I then log out, it does not redirect to the /sign-in page, but remains on the last page. With a downgrade to 14.1.4 this problem does not exist.

P.S. I use [email protected]

I am having the same issue with the URL not changing after a redirect. 14.2.* seems to do this (including 14.2.3 the current latest), but downgrading to 14.1.4 fixes the issue.

If you checkout this branch and then downgrade the Next dep it fixes the e2e test.

devinshoemaker/next-auth-example#20

from next-auth.

I am having the same issue

from next-auth.