Skip to content

Enable Cloudflare Proxy for ecomonetize.com (Lovable-hosted)

When to use this

You purchased Cloudflare for CDN, WAF, and DDoS protection features. Currently ecomonetize.com and www are set to DNS only, which means traffic goes directly to Lovable's servers without passing through Cloudflare's security layer.

This playbook switches the root domain to Proxied (orange cloud) so Cloudflare's security features are active. It requires a specific reconnection step in Lovable — otherwise Lovable shows the domain as "Offline."

Current state (as of 2026-04-22)

Record Type Points to Proxy
ecomonetize.com A 185.158.133.1 (Lovable) DNS only
www A 185.158.133.1 (Lovable) DNS only
docs CNAME eco-docs-internal.pages.dev Proxied

Why Lovable needs a special step

When DNS is proxied, Cloudflare's edge IPs replace the direct A record. Lovable provisions SSL certificates based on the A record pointing to their server. If you just flip the proxy toggle, Lovable sees the domain go "offline" because it can no longer verify ownership via the direct IP.

The fix: reconnect the domain in Lovable using CNAME-based verification, which works with proxied DNS.

Step 1 — Remove the domain in Lovable

  1. Go to lovable.dev → open the ecomonetize.com project
  2. Project Settings → Domains
  3. Remove ecomonetize.com and www.ecomonetize.com

Step 2 — Reconnect with proxy mode enabled

Do this for ecomonetize.com first, then repeat for www.ecomonetize.com:

  1. Click Connect Domain
  2. Enter ecomonetize.com
  3. Expand the Advanced section
  4. Check "Domain uses Cloudflare or a similar proxy"
  5. Save

Lovable will now provide a CNAME record (not an A record) to add to your DNS.

Step 3 — Update DNS records in Cloudflare

In Cloudflare → ecomonetize.com → DNS → Records:

  1. Delete the existing A records for ecomonetize.com and www (pointing to 185.158.133.1)
  2. Add the CNAME records Lovable provides for each
  3. Set both CNAMEs to Proxied (orange cloud)

Traffic flow after this change: User → Cloudflare CDN → Lovable

Step 4 — Verify

  • ecomonetize.com loads correctly in browser
  • Lovable dashboard shows domain as Active (not Offline)
  • Check whatsmydns.net — ecomonetize.com should resolve to Cloudflare IPs (104.x.x.x / 172.x.x.x), not 185.158.133.1

What Cloudflare proxy gives you

  • CDN — static assets cached at Cloudflare edge globally, faster load times
  • DDoS protection — automatic mitigation at Cloudflare's network layer
  • WAF — Web Application Firewall rules (available on paid plans)
  • Analytics — traffic and threat analytics in Cloudflare dashboard
  • SSL — Cloudflare manages SSL instead of Lovable (no change for end users)

Important: docs CNAME is unaffected

The docs CNAME → eco-docs-internal.pages.dev must stay Proxied at all times. Do not change it during this process.

Rollback

If anything breaks, reverse the steps: 1. In Lovable: remove the domain, re-add without the Cloudflare proxy checkbox 2. In Cloudflare DNS: delete the CNAMEs, add back A records for ecomonetize.com and www pointing to 185.158.133.1, set both to DNS only

Last verified

2026-04-22 — documentation.engineering. Guidance sourced from Lovable support during live DNS troubleshooting.