Why this happens
When your custom domain is set as the primary domain in Lovable.dev, it tries to redirect all traffic to that domain. But LovableHTML also handles traffic for that same domain — so they end up sending visitors back and forth forever.
The browser detects this loop and shows "ERR_TOO_MANY_REDIRECTS" or similar.
The fix: Unset your custom domain as primary
You don't need to remove your domain — just tell Lovable.dev to stop treating it as the main one. Here's how:
- Open your project in Lovable.dev
- Open Settings — use Cmd+K (Mac) or Ctrl+K (Windows), then search for "Settings"
- Click on Domains in the left sidebar
- Look at your custom domain — if it has a star icon ⭐ next to it, that means it's set as primary (this is what's causing the issue)
- Click the three dots (⋮) next to your custom domain
- Click Unset as primary
How to tell it worked: After this change, there should be no star icon next to your custom domain. And when you click the three dots (⋮), you should see "Set as primary" (not "Unset as primary").
What stays the same
Your custom domain keeps working exactly as before — nothing breaks. You get these added benefits through LovableHTML:
- Fast load times — served from edge locations worldwide
- Better availability — built on Cloudflare infrastructure
- Crawler analytics — see which bots visit your site and when
Still seeing the error? Try clearing your browser cache or testing in incognito mode. The redirect loop may be cached in your browser.
How LovableHTML handles your traffic
After unsetting as primary, requests flow like this:
- Visitor requests your custom domain
- LovableHTML receives the request
- For bots: serves pre-rendered HTML instantly
- For humans: proxies to your lovable.app origin URL
Your lovable.app URL (e.g., my-project.lovable.app) continues to be the source of truth for your site content.
