Next Auth ([...nextauth] route.ts) Doesn't work on Localhost

[josephna76]

The sign-up works but the sign-in doesn't on Localhost. Both sign-in and sign-up work on Vercel's hosted version.
The project was created using the one-click deployment to Vercel on Jun 23, 2023.

The message "Signed in as X" appears but the three dot loading state over the Sign In button does not end and the page gets stuck before getting to /protected.

I get this error - error TypeError [ERR_INVALID_URL]: Invalid URL. Am I unable to reach /protected despite being signed in because localhost is not an https route, whereas the Vercel deployed version is? http://localhost:3000/

[OldTucson]

same problem

[OldTucson]

The sign-up works but the sign-in doesn't on Localhost. Both sign-in and sign-up work on Vercel's hosted version. The project was created using the one-click deployment to Vercel on Jun 23, 2023.

The message "Signed in as X" appears but the three dot loading state over the Sign In button does not end and the page gets stuck before getting to /protected.

I get this error - error TypeError [ERR_INVALID_URL]: Invalid URL. Am I unable to reach /protected despite being signed in because localhost is not an https route, whereas the Vercel deployed version is? http://localhost:3000/

i just fixed it by add

NEXTAUTH_URL="http://localhost:3000"

to .env file

refer to https://next-auth.js.org/tutorials/securing-pages-and-api-routes#using-gettoken

[raychz]

Still doesnt work for me, even after setting NEXTAUTH_URL="http://localhost:3000/".

EDIT:
The issue was with the versions of next and next-auth that I was using. Seems like a bug in one of the newer updates, potentially related to nextauthjs/next-auth#7638.

The following versions work as expected:

    "next": "^13.4.2",
    "next-auth": "^4.22.1",

The following versions do NOT work as expected (ie, the three dot loading state over the Sign In button does not end and the page gets stuck before getting to /protected):

    "next": "^13.4.19",
    "next-auth": "^4.23.1",

[rlfrahm]

The problem for me was that I had Vercel="1" in my .env file. Removing that solved my issue. This value came from vercel env pull .env automatically.

[leerob]

I am no longer seeing this with the new NextAuth.js beta #48