V5 Beta 30 crashes machine #13381

jtuchel · 2026-02-15T17:11:46Z

jtuchel
Feb 15, 2026

I started with a new Next project using version 16 and want to setup next-auth ( v5 beta 30 ) for Google. For the database I want to use my Supabase instance ( with the schema described here https://authjs.dev/getting-started/adapters/supabase )

Reproduction sandbox: https://stackblitz.com/edit/stackblitz-starters-4xyfndf5

My .env file is following the required next-auth pattern

AUTH_SECRET...
AUTH_GOOGLE_ID=...
AUTH_GOOGLE_SECRET=...
AUTH_GITHUB_ID=...
AUTH_GITHUB_SECRET=...
SUPABASE_URL=...
SUPABASE_SERVICE_ROLE_KEY=...

I started with the auth.ts file in the root dir and passed my own sign in page to the pages field

import { SupabaseAdapter } from "@auth/supabase-adapter";
import NextAuth from "next-auth";
import type { Provider } from "next-auth/providers";
import GoogleProvider from "next-auth/providers/google";

export const providers: Provider[] = [GoogleProvider];

export const { handlers, signIn, signOut, auth } = NextAuth({
	providers,
	pages: {
		signIn: "/sign-in",
	},
	adapter: SupabaseAdapter({
		url: process.env.SUPABASE_URL!,
		secret: process.env.SUPABASE_SERVICE_ROLE_KEY!,
	}),
});

and registered a route at ./app/api/auth/[...nextauth]/route.ts

import { handlers } from "../../../../auth";

export const { GET, POST } = handlers;

Next I created a SessionProvider

"use client";

import { SessionProvider } from "next-auth/react";

export function Providers({ children }: { children: React.ReactNode }) {
	return <SessionProvider>{children}</SessionProvider>;
}

and added it to the root layout

import { Providers } from "../components/providers";

export default function RootLayout({
	children,
}: Readonly<{
	children: React.ReactNode;
}>) {
	return (
		<html lang="en">
			<body>
				<Providers>
					{children}
				</Providers>
			</body>
		</html>
	);
}

Finally I got this sign-in page

import { redirect } from "next/navigation";
import { auth, providers, signIn } from "../../auth";

export default async function SignInPage({
	searchParams,
}: {
	searchParams: Promise<{ [key: string]: string | string[] | undefined }>;
}) {
	const session = await auth();
	const callbackURL =
		((await searchParams)["callback-url"] as string | undefined) ?? "/";

	if (session) {
		redirect(callbackURL);
	}

	return (
		<div>
			{providers.map((provider) => (
				<form
					key={provider.name}
					action={async () => {
						"use server";

						await signIn(provider.options?.id as string, {
							redirectTo: callbackURL,
						});
					}}
				>
					<button type="submit">
						<span>Sign in with {provider.name}</span>
					</button>
				</form>
			))}
		</div>
	);
}

Now when starting the application and navigating to http://localhost:3000/sign-in I click the "Sign in with Google" button for the first time. The URL immediately changes to http://localhost:3000/api/auth/signin?callbackUrl=%2F but nothing happens.

When I click a second time the system crashes with a runtime error

An unexpected response was received from the server.

and the console shows

[auth][error] MissingCSRF: CSRF token was missing during an action signin. Read more at https://errors.authjs.dev#missingcsrf

How can I fix this?

Often enough the whole machine freezes / crashes.

wesleysmyth · 2026-02-18T14:42:10Z

wesleysmyth
Feb 18, 2026

This is likely a memory issue caused by the Supabase adapter + Prisma client initialization loop. Here's what typically happens:

Common causes

1. Prisma client instantiation in dev mode:

In development, Next.js hot-reloads modules, which can create multiple Prisma client instances. Each one opens a connection pool. With the Supabase adapter, this compounds quickly.

Fix — use a singleton:

// lib/prisma.ts
import { PrismaClient } from "@prisma/client";

const globalForPrisma = globalThis as unknown as {
  prisma: PrismaClient | undefined;
};

export const prisma = globalForPrisma.prisma ?? new PrismaClient();

if (process.env.NODE_ENV !== "production") {
  globalForPrisma.prisma = prisma;
}

2. Direct Postgres connection to Supabase without pooling:

If you're connecting directly to Supabase Postgres (port 5432), each Prisma client opens its own connection pool. Use the connection pooler URL instead (port 6543):

# .env
# Use pooler URL (port 6543), NOT direct (port 5432)
DATABASE_URL="postgresql://postgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:6543/postgres?pgbouncer=true"

# Direct URL only for migrations
DIRECT_URL="postgresql://postgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:5432/postgres"

// schema.prisma
datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

3. Auth.js v5 beta + adapter infinite loop:

Some beta versions of Auth.js v5 had a bug where the session callback would trigger a database query, which would trigger the session callback again. Check your auth.ts:

// auth.ts
import NextAuth from "next-auth";
import Google from "next-auth/providers/google";
import { PrismaAdapter } from "@auth/prisma-adapter";
import { prisma } from "./lib/prisma";

export const { handlers, auth, signIn, signOut } = NextAuth({
  adapter: PrismaAdapter(prisma),
  providers: [Google],
  // IMPORTANT: Don't query the DB inside session callback
  // if using the adapter — it already handles this
  callbacks: {
    session: ({ session, user }) => ({
      ...session,
      user: {
        ...session.user,
        id: user.id,
      },
    }),
  },
});

Debugging

Check memory usage:

NODE_OPTIONS="--max-old-space-size=4096" npm run dev

If this prevents the crash, you were running out of heap memory.

Check for connection leaks:

# In Supabase Dashboard > Database > Connections
# See if connections spike when running the app

Minimal working setup for Auth.js v5 + Supabase

// auth.ts
import NextAuth from "next-auth";
import Google from "next-auth/providers/google";
import { SupabaseAdapter } from "@auth/supabase-adapter";

export const { handlers, auth, signIn, signOut } = NextAuth({
  providers: [Google],
  adapter: SupabaseAdapter({
    url: process.env.SUPABASE_URL!,
    secret: process.env.SUPABASE_SERVICE_ROLE_KEY!,
  }),
});

Note: Use @auth/supabase-adapter directly instead of @auth/prisma-adapter with Supabase — it uses the Supabase REST API instead of a direct Postgres connection, avoiding the connection pooling issues entirely.

If the crash persists, share the error output / stack trace and I can narrow it down further.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

V5 Beta 30 crashes machine #13381

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

V5 Beta 30 crashes machine #13381

Uh oh!

Uh oh!

jtuchel Feb 15, 2026

Replies: 1 comment

Uh oh!

wesleysmyth Feb 18, 2026

Common causes

Debugging

Minimal working setup for Auth.js v5 + Supabase

jtuchel
Feb 15, 2026

wesleysmyth
Feb 18, 2026