Signups not working anymore for me

[Cesar-Paredes]

My signups were working fine yesterday and today I'm getting this error:
eEmail address "arrivederchiiiiman@gmail.com" cannot be used as it is not authorized"

I have tried several emails that are not already in my authentication table, I have tried secured passwords using letters, numbers and symbols and it is not working.
Does anyone else getting this error? is this somehow related to the technical issues supabase was having today?

Note that logins are working fine, its only the signups that are not working anymore for me.

[GaryAustin1]

When using the built in SMTP provider all emails need to be part of your organization.
You should see a banner a the top of your dashboard...

[Cesar-Paredes]

I saw that as well but I am not sending emails to my users from my authentication table, look at the screenshot below:
In my providers I don't send any type of email to my users, so the "Auth emails are restricted to your organization's members" do not apply to me.

I debuged further my application and I found more information about the error. Again this error started to happen today but yesterday the signups were working fine.

I dont understand why any email is not authorized to signup, my policies are public.

{
__isAuthError: true,
name: "AuthApiError",
status: 400,
code: "email_address_not_authorized",
}

[GaryAustin1]

It does not matter if you send the email or not currently. The Learn more link has the details.

https://github.com/orgs/supabase/discussions/29370

[Cesar-Paredes]

ok I see. Thanks for the info and taking the time!

Supabase is making this a bit tedious when we are not even trying to use email confirmation, we just want to authenticate but we still have to set up the STMP.

[RodRe1ss]

hi, is there a solution because im just starting to use supabase and im very confused

[GaryAustin1]

@RodRe1ss
If you use the built in SMTP email service your are limited to your dashboard signup email (or dashboard teammates you invite) for app signups. It is just for kicking the tires.

If you are doing more advanced testing and certainly production you need to get your own SMTP provider.

There are some other more advanced cases that are being worked thru the past week because of a change but by the time (and if) they impact you should all be sorted.