Getting auth with HTTP GET not supported

[TheShadowGamer]

Whenever I try to access any /api/auth endpoint, I get the following error: Action auth with HTTP GET is not supported by NextAuth.js. The error seems fairly straight forward, but it occurs when I use the signIn() function from NextAuth.js so I'm not sure what to do. Any help would be appreciated!

[balazsorban44]

That endpoint does not exist. You can find the existing ones here: https://next-auth.js.org/getting-started/rest-api

A reproduction of your code would help resolve your problem.

[TheShadowGamer]

It turns out that I just had the [...nextauth].ts file in the root of the API folder and not in the api/auth folder, sorry 😅

[RGSMTHLS]

This helped me alot

[DatNguyen2711]

oh my fucking god tks broooo :))))))))))))))

[AliceZ413]

haha, I struggled with it until I saw your answer, and then I realized I had done something dumb.

[rafaewaqarqazi]

Thank you 👍

[ezequielsalas]

Yeah, that was the cause

[KyleTryon]

For anyone else who found themselves here and does have their [...nextauth].ts in the right place, this is what happened to me.

Make sure the URL you are hitting is correct. I was visiting /api/auth/signIn (which I think I saw documented somewhere) but the proper URL is shown here: https://next-auth.js.org/getting-started/rest-api, which is /api/auth/signin. Capitalization matters.

[ivangsp]

I had similar problem

[zaheeratwork]

@KyleTryon - Thanks for this awesome. This is exactly the problem I had with document.

[AldinDrobic]

This solved it for me.

[neerajkashetty]

Thanks man!

[LBlend]

I love it when I can trust the documentation....

[B3none]

I've got the same issue as above but my [...nextauth].ts is in the correct place and it works correctly locally.

[GGAlanSmithee]

It's supposed to be [...nextauth].ts. not [...nextauth.ts]

[B3none]

Typo on my part, it’s in the correct place for me and is called the correct name - have corrected

[tibilodon]

Using Turbopack will result in the same error

[JustKira]

same when u went back to webpack it worked just fine i think its problem turbopack

[yanickrochon]

This error started to appear for no apparant reason. No error on the server, but the client fails /api/auth/session with that message. Everything is at the right place.

[jacobcoro]

This error started to appear for no apparant reason. No error on the server, but the client fails /api/auth/session with that message. Everything is at the right place.

Please let me know if you resolve this as I'm having the same issue

[cottons-kr]

This error started to appear for no apparant reason. No error on the server, but the client fails /api/auth/session with that message. Everything is at the right place.

Please let me know if you resolve this as I'm having the same issue

same here

[jacobcoro]

Downgrading my versions of next and next-auth to next@12.3.1 and next-auth@4.14.0 solved this for me as per this suggestion: https://stackoverflow.com/a/74171248

[jacobcoro]

I've had this suddenly start appearing on my production site with no apparent change on my part. It works locally, and also works on my staging site which has the exact same code as production.

I tried the methods above to no avail.

Please help!

[jacobcoro]

Downgrading my versions of next and next-auth to next@12.3.1 and next-auth@4.14.0 solved this for me as per this suggestion: https://stackoverflow.com/a/74171248

[nonfungible-dev]

I was running into this error in NextJS v13.0.6 until I downgraded next-auth to v4.16.0.

After downgrading, I could log in to all the services once again.

[goleary]

After upgrading to NextJS to v13.1.1 & NextAuth v 4.18.7 I am no longer having this error.

I was having problems while on on NextJS v13.0.2 & NextAuth v4.18.4.

[allang]

I'm having this issue on Next 13.1.1 and NextAuth 4.21.1. It's a fresh Next app.

[cottons-kr]

I'm using Next 13.2.4 and Nextauth 4.20.1, then no issue.

[YuriyL-Git]

Could someone check this basic setup. Still getting this error on login button click.
https://github.com/YuriyL-Git/test-auth-app

Setup is done according to official documentation.

[warrenday]

I had this issue when using GitHub for login. My callback URL was https://www.mysite.com/api/auth/callback however changing it to https://mysite.com/api/auth/callback fixed the issue. My env var for NEXTAUTH_URL was always https://mysite.com. So it was all due to a mismatch due to the extra www.

[pmioduszewski]

I'm using credentials provider (JWT + Django). My backend guy changed http -> https which I wasn't aware of. Adding "s" to the URL solved the issue.

[TimothyBrehm]

I had this issue while using App Router instead of Pages. The issue turned out to be [...nextAuth] vs [...nextauth], which is boring,
but the error message still references the pages architecture explicitly, which was a little confusing and obfuscated the issue.

[FtMr1]

By paying attention to the folder arrangement, I resolved the error in pages/api/auth/[...nextauth].ts

[espressom]

If you have correctly set up app/api/auth/[...nextauth]/route.ts in your app router and still encounter the above error, please make sure you have properly registered the endpoint as /api/auth/signin.
I am currently using the following versions:

next: 14.0.3,
next-auth: 4.24.5.

[vladimirhacker]

It didn't help still the same error:
"Error: This action with HTTP POST is not supported by NextAuth.js"

[marsidorowicz]

are you using middleware?

[marsidorowicz]

In next 13+ app router it can be having NEXTAUTH_URL while using middleware, delete key from .env should help u like in my case

[kachar]

Did it solve it for you? I'm using the beta channel and this got broken with the last update to ^5.0.0-beta.9

The logs show:

web:dev: [auth][error] UnknownAction: Cannot parse action at /api/auth/signin .Read more at https://errors.authjs.dev#unknownaction
web:dev:     at parseActionAndProviderId (webpack-internal:///(rsc)/../../node_modules/@auth/core/lib/utils/web.js:90:49)

[marsidorowicz]

Yes, had same errors, also check
Middleware if you follow guidelines

[akash942]

for anyone who is having the same error make sure that the folder is named [...nextauth] and not [nextauth] this will make sure that anything that comes after "auth" in 'yourUrl/api/auth/*' is routed to this folder and the route handler you defined runs. Spent like 4 hours on this :)

[eehhssaan]

Its just folder structure issue. I had pages/api/[nextauth].js (which was wrong). I resolved the issue by just changing the folder structure to pages/api/auth/[nextauth].js