next-auth: 'checks.state argument is missing' error when click back button after authentication with keycloak

I’m also looking for a solution this issue. I’m currently using netlify and originally thought this was an issue with the jwt option, but I keep coming back to this checks option for providers.

Would someone explain what the checks option does? I wasn’t able to find this option in the documentation, so i’m a little stuck as to what it entails.

checking here if someone has found another solution that is not setting checks to none, since that is not secure.

Can with pleasure after an hour of intense testing directly on production on a site that is going viral report that adding checks: ['pkce'] seems to resolve it:

export default NextAuth({
  adapter: PrismaAdapter(prisma),
  providers: [
    GoogleProvider({ clientId: process.env.GOOGLE_CLIENT_ID, clientSecret: process.env.GOOGLE_CLIENT_SECRET, checks: ['pkce'] }),
  ],
  session: { strategy: 'jwt' },
  jwt: { maxAge: 24 * 60 * 60 * 365 }, // 365 days
});

I will talk with my shrink and hope he can calm my nerves after this intense experience 😂.

“KeycloakProvider” has error - type “boths” is missing any updates for this?

Currently experimenting setting up a system using a custom subdomain (app.example.com) & ran into this same issue. Unsure if it will fix / help others but I got mine working by adding checks: "both" to my provider options.

Example:

DiscordProvider({
      checks: "both",
      clientId: "...",
      clientSecret: "...",
}),

Closing as this issue is kinda old. Let’s open a new one with a fresh, minimal reproduction, if it still exists.

@RayBans2111 Have you been able to solve this?

I did! There were a couple of things I needed to check. Make sure that your JWT private key doesn’t have any odd characters or mistypings. This error popped up for me when my JWT private key was wrong.

This error would also appear for me if you are not providing the NEXTAUTH_URL variable in your env files. I troubleshooted this by taking a look at the redirectURLs I was getting, and I was getting a bad url, which somehow resulted in this error.

I did not have to provide “checks” in my next-auth setup at all. Fixing the above would fix the checks error.

Currently experimenting setting up a system using a custom subdomain (app.example.com) & ran into this same issue. Unsure if it will fix / help others but I got mine working by adding checks: "both" to my provider options. Example:

DiscordProvider({
      checks: "both",
      clientId: "...",
      clientSecret: "...",
}),

It works, but also redirects to localhost:3000 instead of my custom domain

is there any workaround to redirect to custom domain instead ???

What if you set NEXTAUTH_URL in the .env file? It worked for me