Sign in

If Google sign-in fails or loops back here

Your NEXT_PUBLIC_* keys can be correct while OAuth still fails — usually a URL mismatch between Supabase, Google, and the address you open in the browser.

1. Supabase → Authentication → URL Configuration: Site URL must match how users open the app (production: https://nourishbyrd.com, or https://www.nourishbyrd.com — pick one canonical host and stick to it).
2. Redirect URLs (same screen): add every origin you use, each with /auth/callback, for example https://nourishbyrd.com/auth/callback, https://www.nourishbyrd.com/auth/callback if you use www, plus http://localhost:3000/auth/callback for local dev.
3. Google Cloud Console → APIs & Services → Credentials → your OAuth client → Authorized redirect URIs must include https://<your-project-ref>.supabase.co/auth/v1/callback (copy the exact URL from Supabase → Authentication → Providers → Google).
4. Open the app at the same host you put in Site URL (don’t mix an old localhost Site URL with nourishbyrd.com in the browser unless both redirect URLs are listed).

After changing dashboard settings, wait a minute, then try an incognito window. Hide this panel.