Guide
Signups not allowed for this instance
How this guide was made: Written with AI assistance and checked against the sources linked on this page.
Updated
Short answer: Supabase shows "Signups not allowed for this instance" when the project setting "Allow new users to sign up" is off. Existing users can still sign in, but no new account can be created. Turn the setting back on in Authentication settings, or, if your app is meant to be invite-only, create users with an admin invite from your server.
What it means
The error comes from Supabase Auth, not from your app code. Its error code is signup_disabled, which the Supabase docs describe as "Sign ups (new account creation) are disabled on the server." The request returns HTTP 422.
It appears in three places:
- Email and password sign-up (
supabase.auth.signUp). - Anonymous sign-in (
supabase.auth.signInAnonymously). - The first sign-in with Google, GitHub or another OAuth provider, for a person who has no account yet. Here the message arrives in the redirect URL as
error=access_denied&error_description=Signups+not+allowed+for+this+instance, so your app may just land on the home or login page with no visible error.
People who already have an account are not affected. That is why the app can seem to work for you and fails for every new visitor.
A close relative is Signups not allowed for otp. That one comes from magic link or OTP sign-in when the code passes shouldCreateUser: false and the email has no account yet.
Causes
| Cause | How to tell | Fix |
|---|---|---|
| "Allow new users to sign up" is off in the project | Dashboard, Authentication settings: the toggle is off. Every new email fails, existing users sign in fine | Turn the toggle on (step 2) |
| It was switched off on purpose to keep the app private | Someone on the team chose invite-only, or the app is an internal tool | Keep it off and invite users from the server (step 4) |
| Local or self-hosted config has sign-ups off | supabase/config.toml has enable_signup = false under [auth], or self-hosted Auth has GOTRUE_DISABLE_SIGNUP=true | Set it to true and restart (step 3) |
| A pushed config switched the hosted project off | Your repo's config.toml has enable_signup = false and was pushed to the project | Fix the file, push again, then check the dashboard |
| Google or GitHub sign-in fails silently for new users | The callback URL contains error=access_denied and the error_description above | Same setting as row 1, then show the error in the UI (step 5) |
Message says for otp, not for this instance | Magic link code passes shouldCreateUser: false | Remove that option or set it to true if new users should get in (step 6) |
How to fix it
- Confirm which message you have. Open your browser DevTools, go to the Network tab, and try to sign up with a new email. Find the request to
/auth/v1/signup(or/auth/v1/otp, or the OAuth callback). The response body will look like this:
{"code":422,"error_code":"signup_disabled","msg":"Signups not allowed for this instance"}
If error_code is signup_disabled, continue with step 2. If the text is Signups not allowed for otp (its error_code is otp_disabled), go to step 6.
- Turn sign-ups back on (hosted Supabase). Before you do this, check that nobody on your team switched it off on purpose. Then open the Supabase dashboard, go to Authentication, open the Sign In / Providers page, find Allow new users to sign up, switch it on and save. While you are there, check that the provider you use (Email, Google, and so on) is also enabled, and if you use guest access, that Allow anonymous sign-ins is on.
- Local development or self-hosted. In
supabase/config.toml:
[auth]
enable_signup = true
[auth.email]
enable_signup = true
Restart with supabase stop then supabase start. For self-hosted Auth, set this environment variable and restart the auth container:
GOTRUE_DISABLE_SIGNUP=false
If you also push this file to the hosted project, push the corrected version so it does not switch sign-ups off again.
- If the app should stay invite-only. Leave sign-ups off and create users from a trusted server, such as an Edge Function or your backend. Admin calls need the secret (service role) key, which must never reach the browser. The invite route does not check the sign-up setting:
import { createClient } from '@supabase/supabase-js'
const admin = createClient(
process.env.SUPABASE_URL!,
process.env.SUPABASE_SECRET_KEY!, // server only
{ auth: { autoRefreshToken: false, persistSession: false } }
)
const { data, error } = await admin.auth.admin.inviteUserByEmail('new.user@example.com')
if (error) throw error
Then remove or hide the public "Sign up" button so visitors don't hit the error.
- Show the error instead of failing silently. For email sign-up:
const { error } = await supabase.auth.signUp({ email, password })
if (error?.code === 'signup_disabled') {
setMessage('New accounts are closed right now. Ask the owner for an invite.')
} else if (error) {
setMessage(error.message)
}
For Google or GitHub sign-in, read the error from the URL on the page your redirect lands on:
const params = new URLSearchParams(window.location.search)
const hash = new URLSearchParams(window.location.hash.slice(1))
const desc = params.get('error_description') ?? hash.get('error_description')
if (desc) setMessage(desc)
- For the
otpvariant. Find the magic link call and removeshouldCreateUser: falseif new users should be able to join this way:
await supabase.auth.signInWithOtp({
email,
options: { emailRedirectTo: `${window.location.origin}/auth/callback` }
})
Keep shouldCreateUser: false only on a login-only screen, and send new users to your sign-up screen instead.
How to check it's fixed
- Open your live app in a private window and sign up with an email address that has never been used. The request to
/auth/v1/signupshould return 200, not 422. - If confirm email is on, the confirmation mail arrives and the link signs you in.
- Try Google or GitHub sign-in with an account that has never used the app. You should end up signed in, and the URL should have no
error=access_denied. - In the dashboard, Authentication, Users: the new user is listed.
- If you chose invite-only, check the reverse: a public sign-up still shows your friendly message, and an invited user can set a password and sign in.
FAQ
Will turning sign-ups back on affect my existing users?
No. The setting only controls whether new accounts can be created. Existing users sign in the same way before and after.
I turned the setting on and still get the error. Why?
Check that you changed the right project. Apps can have a separate project for preview and for production, and the live app's SUPABASE_URL decides which one it talks to. Also check whether a config.toml push or a deploy step is switching it off again.
Can I keep sign-ups closed and still add people?
Yes. Use auth.admin.inviteUserByEmail or auth.admin.createUser from a server with the secret key. Both create accounts even when public sign-ups are off.
---
Still stuck? VibeFix runs a free check on your live app to confirm what's breaking sign-up, then finds the cause, fixes it in your code and re-checks the live app for $79.
Can VibeFix fix it for me?
Yes, for apps built in Lovable or any app whose code is on GitHub. The free check confirms the problem on your live app first. If you want it fixed, our AI agent finds the cause, fixes it in your code for $79 and tests your live app again. See pricing.
Sources
- <https://supabase.com/docs/guides/auth/debugging/error-codes>
- <https://supabase.com/docs/guides/auth/general-configuration>
- <https://github.com/supabase/auth/blob/master/internal/api/signup.go>
- <https://github.com/supabase/auth/blob/master/internal/api/anonymous.go>
- <https://github.com/supabase/auth/blob/master/internal/api/external.go>
- <https://github.com/supabase/auth/blob/master/internal/api/otp.go>
- <https://github.com/supabase/auth/blob/master/internal/api/invite.go>
- <https://supabase.com/docs/guides/local-development/cli/config>
- <https://supabase.com/docs/reference/javascript/admin-api>
- <https://supabase.com/docs/reference/javascript/auth-admin-inviteuserbyemail>
- <https://supabase.com/dashboard/project/_/auth/providers>
- <https://github.com/supabase/auth/blob/master/internal/api/apierrors/apierrors.go>
- <https://github.com/supabase/auth/blob/master/internal/api/admin.go>
- <https://supabase.com/docs/reference/cli/supabase-config-push>
Last checked: 16 November 2026.
VibeFix is independent. Supabase and Stripe are trademarks of their owners.
Want it fixed?
Our AI agent fixes it in your code for $79 and tests your live app again. If we can't complete your re-check, you get your money back.
It starts with a free check that confirms the problem on your live app, no account needed.
More guides · Shopify store accessibility · About · Your privacy choices