Auth data is not present on serverside - NextJS App Router

TL;DR

Fix: do not send unrelated Authorization headers to Clerk-protected routes, or ensure the header carries a valid Clerk JWT.

Steps

1. Contributor jescalan (after the reporter contacted support): the requests carried an Authorization header that did not contain a Clerk JWT. Clerk treats a present Authorization header as the auth token, so verification fails and auth() returns null. Fix: do not send unrelated Authorization headers to Clerk-protected routes, or ensure the header carries a valid Clerk JWT.

When to use

You are seeing this: auth() and currentUser() return null on the server side in the Next.js App Router, even though the user is signed in client-side. Use this skill when you run into "Auth data is not present on serverside - NextJS App Router".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In gh:clerk/javascript#1528 (https://github.com/clerk/javascript/issues/1528), the question was: auth() and currentUser() return null on the server side in the Next.js App Router, even though the user is signed in client-side. The verified resolution: Contributor jescalan (after the reporter contacted support): the requests carried an Authorization header that did not contain a Clerk JWT. Clerk treats a present Authorization header as the auth token, so verification fails and auth() returns null.