Authentication Redirect Configuration Required

You should not normally arrive at this page.
An application using the shared Supabase environment attempted to redirect you after an authentication action, but the requested return URL was not accepted. Supabase therefore sent you to this fallback page instead.

Most likely fix

The application's current URL is probably missing from the list of permitted redirect URLs.

Check:

Supabase → Authentication → URL Configuration → Redirect URLs
Make sure the application's current production URL, custom domain, and any required authentication callback URLs are present.

Other possible causes

The redirect may also have failed because:
The application has recently been deployed under a new Vercel URL.

• A custom domain has been added, changed, or removed.
• A Vercel preview deployment URL is not permitted.
• A password-reset callback URL is missing.
• An email-confirmation callback URL is missing.
• An OAuth callback URL is missing or incorrect.
• The application is sending the wrong redirect URL to Supabase.
• The URL contains the wrong protocol, hostname, domain, port, or path.
• An old application URL is still being used.
• The application is connected to the wrong Supabase project or environment.
• Vercel environment variables contain incorrect Supabase configuration.
• The application's authentication callback configuration is incorrect.
• An authentication email or link was generated using an old or incorrect redirect destination.
• A development or preview environment is trying to use a URL that has not been allowed in Supabase.

Shared Supabase environment

Multiple applications use the same Supabase project for database and authentication services.
The Site URL for this Supabase project deliberately points to this diagnostic page.

Individual applications are expected to:

• Have their permitted URLs registered under Supabase Redirect URLs.
• Explicitly send the correct redirect destination when starting authentication flows.
• Use the correct production, development, preview, or custom-domain URL for the environment being used.

Reaching this page therefore usually means that one of those application-specific settings is missing, outdated, or incorrect.

What to check

• Identify which application initiated the authentication request.
• Confirm the application's current production or custom-domain URL.
• Open Supabase → Authentication → URL Configuration.
• Check that the application's URL is present under Redirect URLs.
• Check that the application is explicitly passing the intended redirect URL to Supabase.
• Check any password-reset, email-confirmation, magic-link, or OAuth callback paths used by the application.
• Check whether a new Vercel deployment or preview URL has recently been created.
• Check the application's Vercel environment variables and confirm they reference the intended Supabase project.
• Correct any missing or outdated URL configuration.
• Retry the authentication action.

Configuration Fallback

This page exists deliberately so that authentication redirect configuration problems are obvious rather than silently redirecting to an unrelated application.
If you are an end user and have reached this page unexpectedly, report the issue to the application owner.