Lovable Login Not Working After Adding a Custom Domain
Quick answer
Sign-in failures on a new Lovable domain usually mean the domain is missing from the auth redirect URLs, and from the OAuth provider's allowed redirect URIs if you use social login.
Most likely fix: Add the domain to auth redirect URLs
How to fix it
Try these in order — the most common fix is first.
1. Add the domain to auth redirect URLs
- Open the authentication settings (the Supabase dashboard, Authentication, if you use Supabase)
- Add your custom domain to the allowed redirect URLs
Did this fix it?2. Update the social login provider
- In the provider console, add the new domain to authorized redirect URIs
- Test sign-in again
Did this fix it?3. Clear the cache
- Hard refresh the page or test in a private window
- Republish with Publish, then Update
Did this fix it?
Symptoms
Login or social sign-in fails or redirects to the wrong address on the custom domain, but works on the lovable.app address.
Why it happens
- New domain missing from auth redirect URLs
- OAuth provider does not recognize the new domain
- Cached old site
This guide also covers
- lovable login not working custom domain
- lovable auth redirect url
- lovable google sign in custom domain
Still not working?
If Lovable keeps failing, you're not alone. See every Lovable problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to us