You (or a friend, or a real customer) try to create an account on your site and get this:
Signups not allowed for this instance- or a generic "Something went wrong", with
signup_disabledin the network response - or, after "Continue with Google", you land back on your site with
error=access_denied&error_code=signup_disabledin the address bar
Meanwhile you can log in fine, and so can everyone who already has an account. That's the clue. Supabase's error code list describes signup_disabled in one line: sign ups (new account creation) are disabled on the server. Your site is up, login works, and nobody new can get in.
This guide shows where that switch lives (there are three places it can be turned off), how to tell it apart from look-alike errors, and what to do if you closed sign-ups on purpose. It applies to sites built with Lovable, Bolt, v0, Replit and Cursor that use Supabase or Lovable's built-in backend.
Step 1: confirm it's really signup_disabled
Open your live site in a private window with DevTools open on the Network tab. Try to sign up with an email address that has never been used. Click the failing request (usually /auth/v1/signup) and read the response.
| What you see | Error code | What it means |
|---|---|---|
Signups not allowed for this instance (HTTP 422) | signup_disabled | New accounts are switched off for the whole project. This guide. |
Email signups are disabled | email_provider_disabled | Only the email and password method is off. See Step 4. |
Signups not allowed for otp | otp_disabled | A magic link or code was requested for an email with no account, and your code told Supabase not to create one. See Step 5. |
User already registered | user_already_exists | The account exists already. See the user already registered guide. |
captcha verification process failed | captcha_failed | CAPTCHA protection blocked the request. See the CAPTCHA guide. |
Supabase's own advice is to branch on error.code, not on the message text, because messages can change. If your sign-up form only shows "Something went wrong", that's the first thing to fix: show (or at least log) the code, so the next failure tells you what it is.
Step 2: find which backend your site really uses
This is where most people lose an hour. There are two different places the sign-up switch can live, and changing the wrong one does nothing.
- Lovable's built-in backend (Lovable Cloud). Users, tables and auth settings are inside Lovable, under the Users view.
- Your own Supabase project. Users and settings are in the Supabase dashboard of that project.
How to tell: open the published site, find any request to *.supabase.co in the Network tab, and note the project reference (the first part of the hostname). If you have a Supabase account, check whether that reference matches one of your projects. If it doesn't, your site is on the built-in backend and the Supabase dashboard you're looking at is not the one your site talks to.
Also watch for two Supabase projects: a test project and a production project. The live site may point at a different project from the one you've been changing. The URL in the live site's requests is the source of truth.
Step 3: turn new sign-ups back on (if you want them)
Pick the place that matches what you found in Step 2.
Lovable built-in backend. Open More, then Users, then Settings. Lovable's docs list two sign-up controls on that form. The one you want is Disable sign-up. When it's on, new users can't sign up, existing users can still sign in, and you can still add people yourself with Add user. Turn it off and save. If you ask Lovable in the chat to "lock down" or "secure" your site, it may have switched this on for you, so check it even if you don't remember touching it.
Your own Supabase project. In the Supabase dashboard, open the Authentication settings for sign-ups and find Allow new users to sign up. Supabase's description says that if this is disabled, only existing users can sign in. Turn it on and save. It takes effect for the next request, and there's nothing to redeploy.
Local development with the Supabase CLI. Locally, the dashboard switch doesn't apply. Sign-ups follow supabase/config.toml:
[auth]
enable_signup = true
[auth.email]
enable_signup = true
Both default to true, so look for one that was set to false, change it, and restart the local stack. Note that this file controls your local setup only, not your hosted production project. If sign-up works on your machine but not on the live site, the live project's dashboard switch is off.
Then test again in a private window with a brand-new email address. If you now get a different error, that's progress. The usual next ones are a confirmation email that never arrives (see signup emails not arriving) or a database error from a trigger that creates a profile row.
Step 4: "Email signups are disabled" is a different switch
If the code is email_provider_disabled, the project-wide switch is fine but the email and password method itself is turned off. Supabase describes it as sign-ups being disabled for email and password.
Turn the Email provider back on in the sign-in methods list (Lovable: Users, then Settings, where each method shows Enabled or Disabled; Supabase: the Email provider settings). Be careful with the local [auth.email] enable_signup key: setting it to false switches off the email method entirely, so existing users can't sign in with email and password either. If what you actually want is "no new accounts", use the top-level [auth] key instead.
If existing users also can't log in, you're probably looking at a sign-in problem rather than a sign-up one. The invalid login credentials guide covers that side.
Step 5: other ways new users hit the same wall
The switch blocks any request that would create a new user, not only the sign-up form. That's why the error can show up in places you didn't expect.
Google, GitHub and other social sign-in. The first time someone signs in with Google, Supabase creates a new user. With sign-ups off, they're sent back to your redirect URL with error=access_denied and error_code=signup_disabled in the query string. People who already have an account sign in normally. If your site ignores those query parameters, the visitor just sees the homepage and assumes the button is broken. Read them on your callback page and show a clear message.
Magic links and email codes. Asking for a magic link with an email that has no account creates the user on first use, so it can be refused too. Separately, if your code passes shouldCreateUser: false, Supabase replies with Signups not allowed for otp (code otp_disabled) for unknown emails. That one is fixed in your code, not in the dashboard: either let the request create the user, or send new people to the normal sign-up form first.
Guest or anonymous sessions. An anonymous user is still a new user. If your site starts a guest session for checkout or a try-before-you-sign-up flow, closing sign-ups can break that too. Lovable lists "Enable anonymous users" right next to "Disable sign-up" for this reason. Check both together.
Invites keep working. Inviting someone from the dashboard, or with Add user in Lovable, still creates accounts while public sign-up is off. That's the intended way to run an invite-only site.
Step 6: if you closed sign-ups on purpose
Sometimes the error is the gate doing its job: a private dashboard, a members-only area, a site that's still in testing. Then the fix isn't the switch, it's the experience around it.
- Remove or hide the public sign-up form. Leaving a form that always fails looks broken and costs you trust with the people who do find it.
- Show a clear message. If someone does reach a sign-up path, catch
signup_disabledand say something like "Accounts are invite-only right now. Contact us for access." Don't pretend the account was created. - Add people yourself. Use Add user (Lovable) or invites (Supabase). Lovable says users created with Add user are confirmed automatically, which avoids email problems for your first users.
- Check your data rules. Closing sign-ups stops strangers from creating accounts, but anyone who signs in can still read whatever your rules allow "authenticated" users to read. If the site has different kinds of users, make sure your row level security limits each row to the right people.
A prompt you can paste into your builder:
My sign-up form shows "Signups not allowed for this instance" (code signup_disabled). Sign-ups are meant to be [open to everyone / invite-only]. If open: tell me exactly which setting to change for the backend this project uses and don't change any database rules. If invite-only: remove the public sign-up form and links, show "Accounts are invite-only right now" when signup_disabled comes back, read error and error_code from the URL on the social sign-in callback page and show the same message, and keep the login form unchanged.
How to confirm it's fixed
- Open the live site (not the editor preview) in a private window.
- Sign up with an email address that has never been used. You should get the expected next step: a "check your email" message, or straight into the site if email confirmation is off.
- If you offer Google or another social sign-in, try it with an account that has never used your site.
- Log in with an existing account to make sure you didn't switch off something your current users need.
- Clean up the test accounts afterwards.
For the full post-publish routine, see how to test a Lovable site after publishing.
Catch it before your users do
A closed sign-up switch is invisible to you: you're already logged in, so everything looks fine, and new visitors don't email to complain. They just leave. Run the free FlowCanary check on your live URL to see the console errors and failed requests a real visitor's browser hits. For ongoing coverage, FlowCanary offers Daily monitoring of your signup, login and checkout (in development; founding spots $19/month, price locked for life, full refund on request any time before it launches).
Further reading
- Supabase Says "Invalid login credentials"? Find the Real Cause and Fix It
- Supabase "User already registered"? Handle Repeat Signups the Right Way
- How to Test a Lovable Site After Publishing: A Step-by-Step Checklist
- Supabase Auth Broke After Deploy? The Usual Suspects, in Order
- Sign-up emails not arriving after launch? Fix your auth email setup
- Lovable site health check
