admin login loop. not able to access admin backend

[winwhereyouare]

Having trouble fixing the admin login loop. when i try to log on to the admin page, it just loops back to the same page after pressing continue with gmail and entered password

[GaryAustin1]

Is the admin page the Supabase Dashboard?

Try a different browser/VPN/device.

[winwhereyouare]

No. the error says: Some exchanges fail: “Unable to exchange external code”

[winwhereyouare]

i tried, mobile, different device....

[GaryAustin1]

Then support@supabase.com

[winwhereyouare]

thanks for the followup.

[harrysun2006]

A login loop after OAuth almost always means the session isn't being persisted after the redirect. If you're using @supabase/ssr, you have to exchange the code for a session in your callback route and write the auth cookies:

// app/auth/callback/route.ts
const { searchParams } = new URL(request.url)
const code = searchParams.get('code')
if (code) await supabase.auth.exchangeCodeForSession(code)

Also check:

• Auth → URL Configuration: Site URL + Redirect URLs contain your exact domain.
• The callback handler runs server-side and actually sets the cookies.
• Third-party cookie blocking isn't dropping the session (test in incognito).
• No clock skew on the machine.

If the loop is on the Supabase dashboard itself (not your own app), it's usually browser-side: try incognito, disable extensions, and allow cookies for supabase.com.

[winwhereyouare]

the number of callback hits= 1/56

302 | document / Redirect | accounts.google.com/signin/oauth/consent?authuser=2&part=AJi8hANMXiDUxN0uYR…AAZBmlqwnp2wWa3X37Y9TKUxa6JJcH2ee5mE4-tqw201PLdNsy3-BLq6nmrgE_c2D5V9YhzMI4 | 0.8 kB | 595 ms

url error description from url : https://www.appNAME.com/auth?error=server_error&error_code=unexpected_failure&error_description=Unable+to+exchange+external+code%3A+4%2F0A#error=server_error&error_code=unexpected_failure&error_description=Unable+to+exchange+external+code%253A+4%252F0A&sb=

[harrysun2006]

That's really useful — and it changes the picture. One callback hit means we can drop the double-exchange / Cloudflare-prefetch theory; Google's code isn't being consumed twice. So it's a single, clean exchange that Google itself is rejecting: unexpected_failure: Unable to exchange external code: 4/0A… (the 4/0A… is just Google's normal auth-code prefix, not a truncated code). You reach the consent screen, so the redirect URI is registered fine — the failure is purely GoTrue → Google at the token step.

With the redirect URI confirmed and only one exchange, the usual culprit for that exact error is the client secret:

• Regenerate it in Google Cloud → APIs & Services → Credentials, and paste the fresh value into Supabase → Authentication → Providers → Google (then remove the old secret in Google). A wrong secret makes Google return invalid_client, which GoTrue surfaces as "unable to exchange external code" — and "looks correct" often hides a rotated/expired one.
• I also spotted authuser=2, so you're using a secondary Google account. If your OAuth consent screen is still in Testing, only listed test users can finish the flow — add that account as a test user (or publish the app).

Two quick things: is the consent screen in Testing or In production, and when you say the secret's verified — was it freshly regenerated and re-pasted, or just visually matched? I'd start with a brand-new secret; that's the most common fix once the redirect URI checks out.

[winwhereyouare]

are you using chatgpt to assess this...?

[harrysun2006]

It's from Claude Code. Does it help anyway, or just none-sense?

[winwhereyouare]

sound similar to what Chatgpt has been giving me. But, seriously, i complaints here...it is much appreciated. any help is help....still trying to make this think work

[harrysun2006]

Understand, AI agent sometimes answer questions a kind like in parallel world though. Is this issue related to manual login to supabase dashboard, or is it a login simulation from code programatically for testing or whatever purpose?
I hit similar issues in other products before due to Chrome extensions, brower cache ...

If you are talking about login problem via https://supabase.com/dashboard/org/slug for below dashboard:

If it's the manual login problem, may I trouble you to add more details in the question like: OS, browser, the cloud supabase or self-hosted supabase, supabase plan, and things you've tried (such as Incognito, other browsers ...) etc.