Fix guide · updated 2026-11-11
Lovable published site "Not secure" (browser warning or security scan)
Not secure · Your connection is not private · ERR_TOO_MANY_REDIRECTS · Dangerous site · 2 critical security issues found
"Not secure" can mean two different problems on a Lovable app. The first is the browser: it doesn't trust the connection to your address, so it shows a label next to the address, or a warning page instead of your app. The second is Lovable's own security scan, which says your app has holes, for example "2 critical security issues found" when you publish. The first is about your address. The second is about your data, and the padlock says nothing about it. Lovable's docs say every published URL is served over HTTPS with a certificate Lovable sets up, custom domains included. So when the browser complains, something between your visitor and Lovable isn't finished yet, or points to the wrong place.
First: what exactly do you see?
- "Not secure" next to the address, and the page loads: the page came over plain
http://. Section 1. - A warning page instead of your site: "Your connection is not private" in Chrome, "This Connection Is Not Private" in Safari, "Warning: Potential Security Risk Ahead" in Firefox, often with a code like
NET::ERR_CERT_COMMON_NAME_INVALID. The certificate doesn't cover this address yet. Section 2. - "This page isn't working" and "redirected you too many times" (
ERR_TOO_MANY_REDIRECTS): almost always Cloudflare in front of Lovable. Section 3. - A red page titled "Dangerous site" or "Deceptive site ahead": Google flagged your address. Section 4.
- The publish dialog says "2 critical security issues found" or "3 security findings": that's Lovable's scan of your app, not the browser. Section 5.
- Visitors land on a page titled "Website Takedown Notice": Lovable's Trust & Safety team blocked the site. Nothing below applies. Contact Lovable support.
1. "Not secure" next to the address
Lovable's hosting doesn't leave visitors on plain http://. We checked a live Lovable site: a visit to http:// gets a permanent redirect to https://, and the answer tells the browser to use only HTTPS for that address for the next year. Addresses ending in .lovable.app are also on the list of HTTPS-only domains built into the major browsers, so a browser never even tries them over http://.
So a grey "Not secure" label means the page didn't come from Lovable's hosting. Two usual reasons:
- Your domain still points to your old host, or to your registrar's parking page. Look at the page. Is it really your Lovable app, in its latest version? If you see your old site or a "this domain is registered" page, your DNS records still send visitors somewhere else. Follow Lovable custom domain not working, sections 2 and 5.
- Your domain goes through Cloudflare with encryption turned off. In Cloudflare's SSL/TLS settings, the encryption mode says Off. Cloudflare's docs say this mode "redirects any HTTPS request to plaintext HTTP". Change it to Full (section 3 explains why not Flexible).
If you clicked past a warning page earlier, Chrome also shows "Not secure", in red, with https crossed out. That's a certificate problem: go to section 2.
The padlock is fine, but an image, a script or a call to your API fails. That's mixed content: your page is on https:// and asks for something on http://. According to MDN, today's browsers upgrade images, video and audio to https:// by themselves and block every other kind of request. If the address is an IP number, even images are blocked. Open the Console (right-click → Inspect → Console) and look for lines that start with Mixed Content:. Each one names the blocked address. A typical case: an automation webhook on your own server, like http://203.0.113.7:5678/webhook/…. Your published site can't call it until that server has a domain name and a certificate. Once it does, ask Lovable to replace every http:// address in the code with https://.
2. "Your connection is not private"
The browser got a certificate that doesn't match the address, or no certificate at all. Lovable creates the certificate for you once your DNS records are right. You don't buy one, and Lovable's docs say a certificate from your registrar (Namecheap, GoDaddy and so on) "is not used by Lovable's hosting". Check these in order.
The domain's status. Open Project → Settings → Domains. Until your domain shows Active, the warning is expected. Setting up domain and Finishing up mean Lovable is still checking your records or issuing the certificate. DNS changes can take up to 72 hours to spread. If there's still no certificate after 72 hours, Lovable's docs ask you to contact support.
The other half of your address. Only www.yourdomain.com fails, or only yourdomain.com? When you connect a root domain, the option Redirect www.yourdomain.com → yourdomain.com is on by default, and the domain row shows www included once both addresses work. If you turned the option off, Lovable connected only the root domain, so www has no certificate from Lovable. Connect www.yourdomain.com as well. With the option on, the setup window lists records for both addresses: add both at your DNS provider.
CAA records. These list which companies may issue certificates for your domain. If your domain has CAA records that leave Lovable's certificate companies out, the domain stays on Finishing up or shows a connection warning. Lovable's docs recommend allowing all three companies it uses: Google Trust Services, Let's Encrypt and SSL.com.
0 issue "pki.goog"
0 issue "letsencrypt.org"
0 issue "ssl.com"
Add these at your DNS provider (flag 0, tag issue, the company's domain as the value), or remove your CAA records if nobody needs them anymore. Connecting a subdomain? Check the root domain too, because a subdomain without CAA records of its own follows the root's. Then open the domain's three-dots menu and select Check again.
Only you, or only one network, sees the warning. Open the site on your phone with Wi-Fi off. If it works there, the problem is on your side. Check the date and time on your computer: a wrong clock makes every certificate look expired, and Chrome then shows NET::ERR_CERT_DATE_INVALID. An antivirus that inspects HTTPS, or a company network that does the same, can also cause the warning.
3. "Redirected you too many times" behind Cloudflare
Lovable's hosting sends every http:// request to https://. If Cloudflare's proxy sits in front (orange cloud) and its encryption mode is Flexible, Cloudflare talks to Lovable over plain http://. Lovable answers "use https", Cloudflare asks again over http://, and so on, forever. Cloudflare's docs describe this exact loop: "Redirect loops will occur if your origin server automatically redirects all HTTP requests to HTTPS."
Two ways out. Pick one.
- Keep Cloudflare's proxy. Set the encryption mode to Full, the fix Cloudflare's docs give for this loop. Once your domain shows Active in Lovable, you can move to Full (strict), which also checks Lovable's certificate. In Lovable, the domain should be connected with Advanced → Uses Cloudflare or similar proxy turned on. That mode uses a
CNAMErecord pointing to your project's published address, and Lovable issues the certificates once that record is right. Lovable's docs are clear that in this mode the proxy setup is yours: Lovable doesn't configure, validate or monitor it. - Drop the proxy. Set the DNS records for your Lovable domain to DNS only (grey cloud). Lovable gives the same fix for Cloudflare errors 1001 and 1003.
More on Cloudflare in Lovable custom domain not working, section 3.
4. A red "Dangerous site" page
This page comes from Google Safe Browsing. Google decided the address hosts phishing (a page that tricks people into typing their passwords or card numbers) or something harmful. Chrome, and the other browsers that use Google's list, now warn every visitor. Your certificate isn't the problem, and no setting in Lovable removes the warning. Only Google removes it, after a review.
- Confirm it. Paste your address into Google's Safe Browsing site status page. If you use both your
lovable.appaddress and your own domain, check both. - Get access to Google's report. Add your site to Google Search Console and verify it. Lovable's Google Search Console connector can do the verification for you. Once it's connected, ask in the project chat: "Verify my Lovable app's domain in Google Search Console." It adds the verification tag to your app's HTML, publishes it, and completes the check with Google.
- Read the report and fix everything. In Search Console, Security & Manual Actions → Security issues names the problem and gives example pages. Fix every issue it lists, on every page it names.
- Request a review. When everything is fixed, select Request Review in the same report and describe what you changed. Google says a review takes from a few days to a few weeks.
5. Lovable's scan says your app isn't secure
When you open the publish dialog, Lovable runs a Quick scan that takes about 10 seconds. It checks your database access rules (including row-level security mistakes), your dependencies, and MCP server exposure. The dialog then shows No security issues found, or a count such as 2 critical security issues found. From Lovable's docs: "Findings do not block publishing by default, but you should resolve critical issues before making your app available." If your workspace admin turned on Block publishing with critical issues, you can't publish until the critical findings are resolved.
- Click the scan line to open the Security view. Critical means problems that need your attention immediately. Warning means issues to review and fix if necessary.
- Try to fix on a finding asks Lovable to fix it. Try to fix all sends every open finding in one request. Test your app before you publish the result: a rule that locks the data too tightly breaks the app in a new way, for example with "new row violates row-level security policy" or "permission denied for table".
- The publish dialog doesn't run the Deep scan. Run it from the Security view before you launch. It reviews all your code for problems like exposed secrets, unsafe input handling and authorization gaps. It takes about 4 minutes on a small app and up to 15 on a large one.
Keep the difference in mind: the padlock only means the connection is encrypted. A site with a perfect padlock can still let any visitor read every row of your tables. For the checks a scanner can't do for you, like using your app as a logged-out visitor and as a second user, see the security checklist for vibe-coded apps.
What to send Lovable
Start in the project chat: ask Lovable about the domain. Its docs say it reports the domain's state, how long it has been in that state, which DNS records it expects and whether it can see them. If you need support, send these lines:
Address: https://yourdomain.com (and https://www.yourdomain.com)
Browser message: [the exact text and code, e.g. NET::ERR_CERT_COMMON_NAME_INVALID]
Status in Project → Settings → Domains: [Active / Setting up domain / Finishing up]
DNS managed at: [provider] · Cloudflare proxy: [on / off] · encryption mode: [Off / Flexible / Full / Full (strict)]
Seen by: [everyone / only me / only on one network]
Since: [date and time, and what changed just before]
Still stuck?
Open your site on a phone with Wi-Fi off. If it works there, the problem is your computer, its network or its antivirus (end of section 2). If it fails there too, the problem is your domain's setup or a Google flag, so go back to the list at the top. And until your domain shows Active, your lovable.app address keeps showing your app with a valid padlock: share that one while you wait. Lovable only starts sending visitors from it to your own domain once that domain is Active and set as primary.
Other Lovable app problems? See Fix a Lovable app.