How to fix provider_disabled: OAuth provider is disabled for signup in Supabase

SupabaseBEGINNERHIGHUpdated Dec 29, 2025· 190 views

Supabase throws this error when you attempt OAuth signup with a provider that hasn't been enabled in your project settings. Enable the provider in the Supabase dashboard and verify credentials are correct.

Quick fix

Fixes provider_disabled

https://yourproject.supabase.co/auth/v1/callback
  1. Log in to Supabase dashboard and select your project
  2. Go to Authentication settings
  3. Check if the provider is enabled
  4. Enable the provider and configure credentials
supabase — error
https://yourproject.supabase.co/auth/v1/callback
provider_disabled: OAuth provider is disabled for signup

What this error means

When you call `signInWithOAuth()` or `signUp()` with a social provider (Google, GitHub, Discord, etc.) that is disabled in your Supabase project, the authentication system rejects the request with this error. The error means the OAuth provider—whether Google, GitHub, Apple, or another service—is not configured and activated in your Supabase project's Auth settings. This is a security measure to prevent unauthorized authentication flows. Before users can sign in via social login, you must explicitly enable and configure each provider in the Supabase dashboard.

Typical symptoms

  • OAuth signup redirects fail or return an error message
  • Social login buttons don't work for certain providers
  • Console shows 'provider_disabled' error when attempting OAuth signin
  • Only some OAuth providers work while others fail (some are enabled, others are not)
  • Local development OAuth works but production doesn't (configuration mismatch between environments)

Common causes

  1. The OAuth provider is not enabled in your Supabase project settings
  2. You enabled the provider in one environment (local) but not another (production/staging)
  3. Provider configuration is incomplete (missing Client ID, Client Secret, or Redirect URI)
  4. OAuth credentials were entered but the provider toggle was left off
  5. For self-hosted Supabase, the provider is not configured in config.toml or docker-compose.yml

How to fix "provider_disabled: OAuth provider is disabled for signup"

1Log in to Supabase dashboard and select your project

Navigate to https://app.supabase.com and authenticate with your credentials. Select the project where users are experiencing the OAuth error.

2Go to Authentication settings

In the left sidebar, click on "Authentication" to expand the menu. Then click on "Providers" or navigate directly to the Auth settings section where you see the list of available OAuth providers.

3Check if the provider is enabled

Look for the OAuth provider you're trying to use (Google, GitHub, Discord, etc.). You should see a toggle switch next to each provider name. If the toggle is OFF (grayed out), the provider is disabled and users cannot sign up with it.

4Enable the provider and configure credentials

Click the toggle to enable the provider. A configuration form will appear asking for:
- Client ID: Obtained from the OAuth provider's developer console
- Client Secret: Obtained from the OAuth provider's developer console
- Redirect URI: Usually auto-filled as https://yourproject.supabase.co/auth/v1/callback

If you don't have a Client ID and Secret, you'll need to create an OAuth app in the provider's developer console first (e.g., Google Cloud Console, GitHub Developer Settings, Discord Developer Portal).

5Verify the redirect URI matches your OAuth app settings

In the OAuth provider's developer console, ensure your app's "Authorized Redirect URIs" or "Callback URLs" includes the exact redirect URI shown in Supabase. A mismatch here is a common cause of OAuth failures.

For example, in Google Cloud Console, add:

bash
https://yourproject.supabase.co/auth/v1/callback

In Discord Developer Portal, set the redirect under OAuth2 settings to the same URL.

6Test the OAuth flow

After enabling and configuring the provider, test it in your application. Call:

javascript
const { data, error } = await supabase.auth.signInWithOAuth({
  provider: 'google', // or 'github', 'discord', etc.
  options: {
    redirectTo: 'https://yourapp.com/auth/callback',
  }
});

if (error) {
  console.error('OAuth error:', error);
}

The user should be redirected to the OAuth provider's login screen without seeing the "provider_disabled" error.

7For self-hosted Supabase, check config.toml

If you're running a self-hosted Supabase instance, the error may indicate the provider is not configured in your config.toml file. Add the provider configuration:

toml
[auth.external.google]
enabled = true
client_id = "your-client-id"
secret = "env(GOOGLE_CLIENT_SECRET)"
skip_nonce_check = false

Replace google with the provider name (github, discord, etc.). Then run:

bash
supabase stop
supabase start

This restarts the Auth service with the new provider configuration.

Advanced notes

Multi-Environment Gotcha: Pay careful attention if your app uses multiple Supabase projects (local, staging, production). Each project has its own provider settings. A provider enabled in your local Supabase (via supabase start) may be disabled in your production project, or vice versa.

OAuth Provider Requirements: Each OAuth provider (Google, GitHub, Discord, etc.) has different setup requirements. You must create an OAuth app in each provider's developer console and obtain credentials. This is a one-time setup but varies by provider.

Localhost Development: When developing locally with Supabase, your site_url in supabase/config.toml should be http://localhost:3000 (not http://127.0.0.1:3000), and your OAuth provider's redirect URI should match accordingly.

Session Not Persisted: If OAuth succeeds but the session doesn't persist (user signs in but immediately logs out), verify that your app's redirect callback properly stores the session token. The OAuth callback URL should handle the #access_token=... fragment returned by Supabase.

Frequently asked questions

What does "provider_disabled" mean?
) that is disabled in your Supabase project, the authentication system rejects the request with this error. The error means the OAuth provider—whether Google, GitHub, Apple, or another service—is not configured and activated in your Supabase project's Auth settings. This is a security measure to prevent unauthorized authentication flows.
How do I fix "provider_disabled"?
Supabase throws this error when you attempt OAuth signup with a provider that hasn't been enabled in your project settings. Enable the provider in the Supabase dashboard and verify credentials are correct.
What causes "provider_disabled"?
The OAuth provider is not enabled in your Supabase project settings You enabled the provider in one environment (local) but not another (production/staging) Provider configuration is incomplete (missing Client ID, Client Secret, or Redirect URI)
Is the "provider_disabled" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading