My Lovable app stopped working
When login works in the Lovable preview and fails on the published URL or custom domain, the published address is usually missing from the auth Site URL or Redirect URLs. Confirmation mail fails on its own: until you send from your domain, messages go out from a shared sender, so they are easy to rate-limit and easy to lose in spam. The same symptom also comes from a recent AI edit, a Google consent screen left in testing, a published build pointed at the wrong Supabase project, or a refresh 404 when the app is hosted outside Lovable.
Last updated Nov 15, 2026.
Describe the failure first
Write this down before changing settings. The fix for “nobody can log in on the custom domain” is not the fix for “one new user never got the email.”
- Where: the preview, the published lovable.app address, or the custom domain. Try each. A failure on only one of them is a URL-configuration problem, not a broken password form.
- Who: all users, only new signups, or one account. Existing users can still sign in when sign-up is disabled. One unconfirmed account is an email problem, not an outage.
- When: the last prompt you sent, and the last auth setting you changed. If it broke in the same minute as a publish, start with redirect URLs.
- Evidence: browser console, and the network tab on the auth request. Note 401, 403, or 500, and the host the request went to. A 401 against a different Supabase host than the one you edited means the build is pointed at the wrong project.
Fix it, one cause at a time
Published URL or custom domain missing from auth
Preview and production are different origins. Auth will not send a person back to an origin that is not allowed. Lovable’s own docs say this is the usual reason sign-in works in preview and breaks after publish.
Lovable Cloud (built-in backend)
- Open the project, then More → Users → Settings → Advanced.
- Set Site URL to the address people should land on after sign-in when the app does not pass its own redirect. For a custom domain, that is the custom domain.
- Under Redirect URLs, add the published address and the custom domain. End a web address in /** so every path matches, for example https://app.example.com/**.
- Publish again if you changed domains. Lovable updates these for the built-in backend when you publish and when you connect a domain, but a domain it does not serve is yours to add. You can also ask in the project chat to add the domain.
Your own Supabase project
- In that Supabase project, open Authentication → URL Configuration.
- Set Site URL to the live address, and add the same address to Redirect URLs, including the /** wildcard if you use one.
- Lovable can add its own preview addresses to that project. It does not keep your production Site URL up to date for you. If the app is hosted outside Lovable, add that host yourself.
Confirmation email not arriving
With auto-confirm off, a new account cannot sign in until the address is verified. The message is easy to miss, and easy to mistake for a broken signup form.
- Ask the person to check spam. Mail from a new or shared sender lands there often.
- On Lovable’s built-in backend, open More → Users → Settings → Email. Auto-confirm signs people in without a confirmation message. That is useful while you are testing. For a live app, leave confirmation on so an account belongs to an address someone can read.
- Open More → Users → Settings → Email → Advanced and check Rate limit for sending emails. New projects start at 1,000 auth emails an hour (confirmations, resets, magic links, and invites share that cap). If Lovable says email sending is not active, a higher number does not help: mail is still going through the shared sender, which has its own stricter limit. Set up a custom sending domain under More → Emails first.
- On your own Supabase project, the built-in mailer is for testing and is rate-limited. Add your own SMTP provider in that project’s email settings, and set the same Site URL you fixed above so links in the message point at the live app.
- An old confirmation or reset link keeps the address it was sent with. After you change URLs, do not reuse that message.
- Signing in again does not resend confirmation. The person can sign up again with the same email, or you can use More → Users → Add user → Create new user, which confirms the account for them.
A recent AI edit changed the code or the policies
- Compare the preview with the published app. If the preview is already broken, the last prompt changed the page or the row-level security policies. Read the console error before you prompt again.
- If only new people fail, check Disable sign-up under the auth settings. Existing users can still log in while new signups are blocked.
- Restoring a previous version restores the code. It does not restore the database: users, redirect URLs, and email settings stay as they are. Put those back by hand if that is what changed.
Google sign-in stuck in testing
- If Google is “Managed by Lovable,” you do not have a consent screen to publish. A failure there still starts with redirect URLs, including the custom domain.
- If you used your own Google Cloud OAuth client, open the consent screen. Testing mode only allows the test users you listed, and everyone else gets a warning or a dead end. Add the real user, or publish the consent screen when you are ready for that.
- Add the published app’s redirect URI in Google Cloud Console, then select it in Lovable. A domain that works for email login can still fail Google until that URI exists.
Env vars pointing at the wrong Supabase project
This shows up after you connect your own Supabase project or export the app. The preview can be healthy while the published build still contains the previous project’s URL and public key.
- In the browser network tab, read the host on the failing auth request.
- Compare it with the project where you edited URL Configuration. If they differ, the published site is not talking to the project you fixed.
- Point the published build at that project’s URL and public key, then publish again. Redirect URLs on the unused project do nothing for this site.
Refresh 404s when the app is hosted outside Lovable
Lovable’s own hosting serves the app for client-side routes. Another host often does not. Opening the site at / works, then a refresh on /login or /signup returns 404, because the server looks for a file that was never built.
- Confirm the 404 happens only on the external host, not on the lovable.app address.
- Add a rewrite so unknown paths serve the app’s index file. On Vercel and Netlify that is a SPA fallback. On a static bucket it is an error-document or redirect rule.
- After the rewrite works, come back to redirect URLs. The host has to allow the route, and auth has to allow the origin.
Prove the fix with a new email
- Open a private window. An old session can hide a redirect bug.
- Sign up with an email address that has never been used on this project. Old confirmation links still contain the old address.
- Repeat on the published URL and on the custom domain, not only in preview.
How to catch it next time
Pick the check that matches the failure you care about. A tool that only fetches the homepage will stay green through every item on this page except the refresh 404.
- Manual test after every edit. Publish, then sign up in a private window with a new email, on the URL your customers use. This is accurate. It is also the check people skip when the prompt was “just a copy change.”
- An uptime monitor. It fetches a URL and tells you the status code. That is enough when the host is down, the domain lapsed, or the homepage returns 500. It is not enough when the page loads and signup does not. A broken login often still serves 200 on /.
- Playwright, or any script you maintain. A scripted walk of signup will catch a missing button or a 401. You own the selectors. The next AI edit that renames the form will fail the script until you update it, and nothing runs unless your CI or a cron actually starts it.
- BreakAlarm. You describe signup, login, or checkout once. It re-walks those steps after an AI edit or a deploy, then emails a screenshot and a paste-ready fix prompt. Free checks one app every 24 hours. Starter is three apps, every hour, with a deploy hook. Pro is ten apps, every 15 minutes, with the hook and a Stripe lockout check. A green result only means the steps you wrote passed. It will not tell you that a confirmation landed in the inbox. Use it when the flow that makes money is what you are afraid of shipping broken. Use a plain uptime check when you only care that a URL answers.
The limits are the ones on the pricing section. The homepage explains the product. Create an account if you want it on a schedule.
FAQ
Why does Lovable login work in preview but not on the published app?
The published URL or custom domain is usually missing from Site URL or Redirect URLs. Preview and published are different addresses, and auth will only return to addresses on that list. On Lovable’s built-in backend, open More → Users → Settings → Advanced → Redirect URLs. On your own Supabase project, set the same values under Authentication → URL Configuration.
Why is the Lovable confirmation email not arriving?
Check spam first. Until you send from your own domain, auth mail goes out from a shared sender, and a burst of signups can hit the hourly cap under More → Users → Settings → Email → Advanced. Signing in again does not resend a confirmation. The person can sign up again with the same address, or you can create the user under More → Users → Add user → Create new user, which confirms the account.
Lovable signup broke after a deploy. What should I look at first?
Note whether it fails for everyone, only new people, or one account, and whether it fails on the preview, the published lovable.app address, or the custom domain. Then look at the browser network tab for 401, 403, or 500 on the auth request. A 401 on the published site with a working preview is usually the redirect list or a build still pointed at the wrong Supabase project.
Does restoring a previous Lovable version undo the auth settings?
No. Restoring a previous version puts the code back. It does not roll back users, redirect URLs, or email settings stored in the backend. If the bug was a setting rather than a prompt, restore the setting by hand.
Google sign-in only works for me, or shows a testing warning. Why?
Managed by Lovable Google sign-in does not use your Google Cloud consent screen. If you connected your own OAuth client, that screen may still be in Testing, which lets only listed test users through. Add the published redirect URI in Google Cloud Console as well. Lovable’s auth docs describe that extra step for your own credentials.
Will an uptime monitor catch a broken Lovable signup?
Only if the page itself stops loading. A signup that loads, then fails auth, still returns 200 on the homepage. A ping is enough when you only care that the host is up. It is the wrong tool when the question is whether a new person can create an account.
References
- Lovable: Users and authentication. Site URL, Redirect URLs, and why preview login fails on the published app.
- Lovable: Email authentication. Auto-confirm, the hourly sending limit, and confirmation mail that never arrives.