Lovable app users not getting confirmation emails or stuck unconfirmed

What it means in plain English

With email sign-in, Lovable says "unless auto-confirm is on, they receive a confirmation email and verify the address before they can sign in." If that email never arrives, the person can't sign in.

Lovable's email auth guide lists this as its first troubleshooting item, "Users are not receiving confirmation emails", and gives two reasons: spam filters, since "emails from new domains often land there", and the hourly email rate limit when many people sign up at once.

Which settings you change depends on the backend. Lovable's email settings page applies to apps on the built-in backend. It says "projects connected to your own Supabase project manage authentication in Supabase instead."

Likely causes

• The email went to spam.
• Many sign-ups at once hit the project's hourly email limit. On the built-in backend this is Rate limit for sending emails.
• On your own Supabase project, the default email sender is in use. Supabase says it is "not meant for production use", is "currently" limited to 2 messages per hour, and only delivers to members of the project's team. Every other address fails with "Email address not authorized".
• The confirmation email expired before the user clicked it.

How to fix it, step by step

1. Ask the user to check their spam folder. Lovable says to do this first.
2. Built-in backend: open More → Users → Settings → Email. Under Advanced, check Rate limit for sending emails, which caps how many auth emails your project sends per hour. Lovable says that to raise it, you first set up email sending for the project, "either managed email or a verified custom domain", under More → Emails.
3. Built-in backend, one stuck user: Lovable says signing in again does not resend the email. The user can trigger a new one "by signing up again with the same email address." Or create the account yourself with Add user → Create new user in More → Users. Users added that way are confirmed automatically.
4. Your own Supabase project: set up custom SMTP in the Supabase Authentication settings. Supabase says that once you save it, Auth sends to all addresses, starting at a low limit of 30 messages per hour that you can raise on the Rate Limits page.
5. Your own Supabase project, rate limited: Supabase returns 429 Too Many Requests when a rate limit is exceeded. The code over_email_send_rate_limit means "Too many emails have been sent to this email address." Wait before retrying.
6. Only turn on Auto-confirm email for testing. Lovable warns that without confirmation, "anyone can sign up with an address they don't own." For a Supabase project, Lovable's tip is the same: turn email confirmation off while testing and "re-enable it before launching to real users."

How to check it worked

• A new test sign-up gets the confirmation email in the inbox, and the link signs the user in.
• The user shows as confirmed in More → Users, or under Authentication in the Supabase dashboard.
• If the link opens on the wrong address, fix the redirect URLs. See Lovable sign-in works in preview but fails when published.

Not your symptom? Match other login problems in Lovable authentication errors.

Questions people ask

Why aren't users of my Lovable app getting the confirmation email?

Lovable names two reasons: the email went to spam, since emails from new domains often land there, or many sign-ups at once hit the hourly email rate limit.

How do I resend a confirmation email to one Lovable user?

On the built-in backend, signing in again does not resend it. The user can sign up again with the same email address, or you can create the account with Add user → Create new user in More → Users, which confirms it automatically.

Should I turn on auto-confirm to fix it?

Only for testing. Lovable warns that without confirmation, anyone can sign up with an address they don't own.

Sources

• https://docs.lovable.dev/features/email-auth (opens in a new tab)
• https://docs.lovable.dev/features/authentication (opens in a new tab)
• https://docs.lovable.dev/integrations/supabase (opens in a new tab)
• https://supabase.com/docs/guides/auth/auth-smtp (opens in a new tab)
• https://supabase.com/docs/guides/auth/rate-limits (opens in a new tab)
• https://supabase.com/docs/guides/auth/debugging/error-codes (opens in a new tab)