Fix guide · updated 2026-11-15
Supabase "Signups not allowed for this instance"
AuthApiError: Signups not allowed for this instance · signup_disabled · 422
A new user tries to sign up, or to log in with Google or a magic link for the first time, and Supabase answers "Signups not allowed for this instance". People who already have an account still get in. One switch in your Supabase project decides this, and it's easy to turn off without noticing. Here's where it is, the look-alike errors, and how to open sign-ups safely.
What the error means
We read the Supabase Auth code. When your project doesn't allow new users, every path that would create an account stops with HTTP 422, code signup_disabled, "Signups not allowed for this instance":
signUpwith an email and password, or a phone number,signInWithOtp(magic link or code) for an email that has no account yet,- Google, GitHub or any other OAuth login for someone who has no account yet,
- anonymous sign-ins.
People who already have an account aren't affected: they sign in as usual. And you can still create accounts yourself: invites and admin.auth.admin.createUser don't check this setting. Both need your secret key, so they run on your server: from the browser they fail with "User not allowed".
1. "Allow new users to sign up" is off
In the Supabase dashboard: Authentication → Sign In / Providers → User Signups → Allow new users to sign up. Turn it on, save, and try the sign-up again.
It's usually off on purpose at some point: to keep strangers out of a half-built app, during a demo, or because a template was invite-only. If your app should stay invite-only, leave it off and invite people from the Users page in Authentication instead.
2. Google login sends new users back with nothing on screen
With Google and the other OAuth providers, the error doesn't come back from a call in your code. Supabase sends the person back to your site with the error in the address, both in the query string and after the #:
https://yourapp.com/?error=access_denied&error_code=signup_disabled&error_description=Signups+not+allowed+for+this+instance
If your app ignores those parameters, the person lands back on the login page with no message and tries again, forever. Read error_code and error_description on the page Supabase redirects to, and show a message.
3. "Signups not allowed for otp"
A different code, otp_disabled, and a different cause: your code calls signInWithOtp with shouldCreateUser: false. Supabase then sends a link or code only to emails that already have an account, and answers HTTP 422 "Signups not allowed for otp" for a new one. That's the right setup for a login-only form. If the same form is also how people sign up, remove shouldCreateUser: false (it defaults to true):
await supabase.auth.signInWithOtp({
email,
options: { emailRedirectTo: window.location.origin }, // no shouldCreateUser: false
});
4. "Email signups are disabled"
If the Email provider itself is off (Authentication → Sign In / Providers → Email), email sign-ups answer HTTP 400 "Email signups are disabled" and magic links answer "Email logins are disabled", both with the code email_provider_disabled. Turn the Email provider back on if your app uses email at all.
Is it safe to open sign-ups?
Yes, if your database is protected. Once sign-ups are open, anyone can create an account and get a valid login, so every table needs Row Level Security policies that limit what a signed-in user can read and write. Turning sign-ups off is often a patch over missing policies. Check with our security checklist for vibe-coded apps before you turn the switch back on.
If an AI tool built your app
Give your AI tool this prompt, so people see a clear message instead of a raw error or nothing:
On the sign-up form and the magic link form, when Supabase returns the error code signup_disabled, show "Sign-ups are closed right now." instead of the raw error. On the page Supabase redirects to after Google login, read error_code and error_description from the URL (the query string and the part after #); if error_code is signup_disabled, show the same message, and for any other error show error_description. Don't change anything else.
Then make the real decision yourself in the dashboard: turn "Allow new users to sign up" on (case 1), or keep it off and invite people.
Not quite your error?
- Sign-up says the email is taken: Supabase "User already registered".
- Sign-up says "Anonymous sign-ins are disabled": Supabase "Anonymous sign-ins are disabled".
- Sign-up fails for every new email with a database message: Supabase "Database error saving new user".
- Google login sends people to localhost: Supabase login redirects to localhost.
- Google shows "Error 400: redirect_uri_mismatch": Google login "redirect_uri_mismatch".
- Google login opens a page of JSON with "Unsupported provider": Supabase "Unsupported provider: provider is not enabled".
Still stuck?
If the switch is on and new users still get "Signups not allowed for this instance", make sure your app talks to the project you changed: the Supabase URL in your app's settings must match the dashboard's (see case 1 of our "Invalid login credentials" guide). The Auth logs in your dashboard show each refused request and where it came from: sign-up, magic link or OAuth.
Other Supabase problems? See Supabase fixes.