How to disable email confirm in Self-Hosted

[jgreywolf]

I think the title is pretty self explanatory. But I will add more...

I have seen various discussions such as https://github.com/orgs/supabase/discussions/4444, which explains that the settings UI is not going to be available in the self-hosted version of supabase, instead making use of config files.

So - how do we configure the app to not require email confirmation before allowing users to sign in?

I have customers that are using a self-hosted version of our app. Due to security restrictions they cannot/will not add email to supabase, so we want to turn off email verification in these scenarios.

In which case, how do we turn off email confirmation for self hosted uses?

As an aside, ENABLE_EMAIL_AUTOCONFIRM=true does not seem to be working. And even more annoying is that the kubernetes/helm chart version doesnt seem to even expose this setting...

[GaryAustin1]

https://supabase.com/docs/guides/self-hosting/auth/config

Also note that an email is still required even if confirm is off. It just can be a valid email format fake one.

[jgreywolf]

Thanks for the help so far. It seems like it shouldnt be so hard to turn this feature off for the containerized version

[gbusto]

I had this issue of trying to disable email confirmation on self-hosted. Even with GOTRUE_MAILER_AUTOCONFIRM set to false, it would still try to send one and give me this error: Signup error: Error sending confirmation email. I had to tweak the .env file email auth section to look like this:

## Email auth
ENABLE_EMAIL_SIGNUP=true
ENABLE_EMAIL_AUTOCONFIRM=false
#SMTP_ADMIN_EMAIL=admin@example.com
#SMTP_HOST=supabase-mail
SMTP_PORT=2500
#SMTP_USER=fake_mail_user
#SMTP_PASS=fake_mail_password
#SMTP_SENDER_NAME=fake_sender
ENABLE_ANONYMOUS_USERS=false

Now I don't get that error and things seem to work. But note that SMTP_PORT still needs to be uncommented. Having an empty value for the port caused the supabase-auth service to fail.

It's been a bit of minefield trying to get things setup in self-hosted Supabase. Keeping a list of everything extra I'm having to do so I can share it somewhere to save people some sanity.

[Bvcmbru2024]

I'm about to lose mine, I made a beautiful piece on bolt.new and now cant create a user anymore

[gbusto]

EDIT - I was getting warnings, so the easier thing to do is just set them to blank strings:

## Email auth
ENABLE_EMAIL_SIGNUP=true
ENABLE_EMAIL_AUTOCONFIRM=true
SMTP_ADMIN_EMAIL=
SMTP_HOST=
SMTP_PORT=2500
SMTP_USER=
SMTP_PASS=
SMTP_SENDER_NAME=
ENABLE_ANONYMOUS_USERS=false

Also, set ENABLE_EMAIL_AUTOCONFIRM to false so new users are auto-confirmed.

@Bvcmbru2024 , sorry to hear that. I'm still running into issues too with other stuff. I just spent ~1 hour debugging another weird issue that hadn't come up before. Something to do with SSL and trying to generate types using the supabase cli.

I just shared a quick blog post with my notes and stuff. See if any of this helps you:
https://blog.gbusto.com/self-hosting-supabase-part-1/

[uplg]

Tested right now on a self-hosted Supabase, and SMTP params needs to be there for ENABLE_EMAIL_AUTOCONFIRM=true to work.