Sign-Up Emails Not Arriving in Your AI-Built App
It worked in the preview. On your own domain, new users never get the confirmation email, or the link in it goes nowhere. In apps built on Supabase this is nearly always one of two settings, not your code.
The short answer
If your app was built with Lovable, Bolt, v0 or a similar tool and uses Supabase for sign-in, check two things in the Supabase dashboard before you ask the AI to change any code:
- The email sender. The built-in one is for testing only.
- The URL settings. Your live domain has to be listed.
Setting 1: the email sender
Supabase sends sign-up and password emails through a built-in service until you connect your own. Its documentation is direct about the limits: the built-in service delivers only to addresses on your project's team, sends a small number of emails an hour (2, at the time of writing), and is "not meant for production use". Everyone else gets nothing, or the sign-up fails with "Email address not authorized".
That is why it worked for you and fails for your users. You are on the team.
The fix: connect your own SMTP sender in Supabase, under Authentication, then Emails. Any transactional email provider works. Verify your domain with that provider, so the emails come from your domain and land in inboxes rather than spam. Then sign up with a fresh address that is not on your team.
Setting 2: the URLs
If the email arrives but the link opens the preview, a blank page or an error, look at Authentication, then URL Configuration:
- Site URL should be your live domain, for example
https://yourapp.com. It is the default address the confirmation and password-reset links point to. - Redirect URLs is the allow list. Your live domain needs to be on it, not only the preview address.
After a custom domain goes live, this is the setting most often left behind.
Why asking the AI often makes it worse
The sign-up code is usually fine. Asked to "fix the emails", an AI tool tends to rewrite the sign-up page, which can break something that worked. Change the two settings first, test with a new address, and only then look at the code.
Questions
Do I need a paid email provider?
Most transactional email providers have a free tier that covers an early app. What matters is that the sender is yours and your domain is verified with it.
The email arrives in spam. Why?
Usually the sending domain is not verified with the provider, or the email comes from the provider's own domain. Finish the domain verification steps the provider gives you.
Can I test without real users?
Yes. Sign up with two or three fresh addresses at different email services, including one that is not on your Supabase team, and follow each link to the end.
Still stuck? Get a free first look from a senior engineer. Send the link and what happens, never your keys.
Sources: Supabase documentation, opened November 17, 2026: Send emails with custom SMTP, Redirect URLs.
Emails still not arriving?
Send the link and the tool you built with. A senior engineer replies within one business day with what is wrong and what it takes.
Reply within one business day · No passwords or keys, ever