Why Your Manus Site Shows “Not Secure” After Domain Connection (SSL Fix)

Published By :Iram S. Updated On : Manus AI, AI
📌 Summarize this content with AI
ChatGPT Grok Google AI Perplexity Claude

You spent hours building a beautiful site on Manus. You connected your custom domain, hit publish, typed your URL with excitement — and your browser slaps you with a red “Not Secure” warning. What went wrong?

You’re not alone. The “Not Secure” warning after connecting a custom domain to a Manus site is one of the most common issues new Manus users face. The good news: it’s almost always an SSL certificate problem — and it’s completely fixable.

In this guide, we’ll walk you through exactly why this happens, how to diagnose it, and how to fix the SSL error on your Manus-connected domain — step by step, without needing to be a technical expert.

1. What Does “Not Secure” Actually Mean?

When your browser shows a “Not Secure” warning in the address bar, it means the website you’re visiting is being served over HTTP instead of HTTPS. The difference matters enormously:

  • HTTP — Data travels between the browser and server in plain text. Anyone on the same network can intercept it.
  • HTTPS — Data is encrypted using an SSL/TLS certificate. It’s secure, private, and trusted by browsers.

Getting a free SSL certificate for your website using Cloudflare

An SSL certificate (Secure Sockets Layer) is the digital document that enables HTTPS. Without a valid, properly installed SSL certificate tied to your domain, your site will show the “Not Secure” warning — even if the site itself looks and works perfectly.

This isn’t just a cosmetic issue. Here’s why it matters:

  • Visitors distrust it immediately — Most users will leave a site the moment they see the warning.
  • Google penalizes non-HTTPS sites — It’s a confirmed ranking signal. HTTP sites rank lower.
  • Browsers actively block some content — Chrome, Firefox, and Safari increasingly block non-secure sites from loading certain features.
  • Forms and payments are at risk — Any contact form, checkout, or login on an HTTP site is a liability.

The bottom line: a “Not Secure” warning is a showstopper, and it needs to be fixed before you promote your Manus site to anyone.

2. Why Manus Sites Show This Warning After Domain Connection

Manus is an AI-powered platform for building and deploying websites. When you build a site on Manus and access it through the default Manus subdomain (e.g., yoursite.manus.app), SSL is handled automatically — everything is secure out of the box.

The problem almost always appears the moment you connect a custom domain (e.g., www.yourbusiness.com).

Here’s why:

Reason 1: The SSL Certificate Hasn’t Been Issued Yet for Your Domain

When you connect a custom domain to Manus, the platform needs to issue a new SSL certificate specifically for your domain. This is different from the certificate that covers the manus.app subdomain you used during building.

Manus typically uses an automated SSL provider (like Let’s Encrypt or similar) to generate and install this certificate. But this process isn’t instantaneous — it requires your domain’s DNS records to fully propagate and point correctly to Manus’s servers before the certificate can be validated and issued.

If you visit your custom domain too soon, the certificate may not be ready yet, resulting in the “Not Secure” warning.

Reason 2: DNS Records Are Configured Incorrectly

For Manus to issue an SSL certificate for your domain, your domain’s DNS settings must point to Manus’s servers. Common DNS configuration mistakes include:

  • Pointing only the root domain (yourdomain.com) but forgetting the www subdomain (or vice versa)
  • Adding a CNAME record where an A record is required
  • Leaving old DNS records that conflict with the new Manus settings
  • Entering the Manus IP or CNAME value with a typo

When DNS is misconfigured, Manus can’t complete the SSL verification process, and your site stays insecure.

Reason 3: Cloudflare’s SSL Mode Is Set Incorrectly

Many domain owners use Cloudflare as a DNS manager (and CDN). Cloudflare adds its own layer of SSL handling, and if the SSL/TLS mode in Cloudflare isn’t set correctly, it creates a conflict that causes SSL errors — even if both Cloudflare and Manus technically have certificates.

See also  Top 10 Free Domain Name Generators in 2026

The most dangerous setting here is Flexible SSL, which we’ll cover in detail later.

Reason 4: Mixed Content Issues

Sometimes your domain and SSL certificate are fine — but specific pages or elements on your site load resources (images, scripts, stylesheets) over HTTP instead of HTTPS. This is called a mixed content error and will still trigger a “Not Secure” warning or a broken padlock icon even with a valid SSL certificate.

Reason 5: SSL Certificate Has Expired

SSL certificates aren’t permanent. They typically expire every 90 days (for free Let’s Encrypt certificates) or every 1–2 years (for paid certificates). If auto-renewal fails, your site will suddenly show as “Not Secure” even though it was previously secure.

Getting a free SSL certificate for your website using Cloudflare

3. The Role of DNS Propagation

Before we get into the fix, it’s important to understand DNS propagation — because rushing this step is the #1 cause of confusion and frustration.

DNS propagation is the time it takes for changes to your domain’s DNS settings to spread across all DNS servers worldwide. When you update your DNS records to point to Manus, that change doesn’t happen instantly everywhere on the internet.

Propagation can take anywhere from a few minutes to 48 hours, depending on:

  • Your domain registrar (GoDaddy, Namecheap, Google Domains, etc.)
  • Your TTL (Time to Live) settings — how long DNS servers cache your old records
  • Your ISP and geographic location

During this propagation window, some users will see your site correctly (via servers that already have the new DNS info), while others (including possibly you) might still see the old configuration — or an SSL error.

What to do: After making DNS changes, wait at least 24 hours before diagnosing a problem. Use a tool like DNSChecker.org to see whether your DNS has propagated globally before troubleshooting further.

4. How to Diagnose Your SSL Problem

Before jumping to fixes, let’s figure out exactly what’s going wrong. Here’s a quick diagnostic checklist:

Step 1: Check Your SSL Certificate Status

Visit SSL Labs’ SSL Test and enter your domain. This free tool will give you a full report on your SSL certificate — whether it exists, who issued it, when it expires, and any errors.

  • Grade A or B — SSL is working. Your issue might be mixed content (see Step 4).
  • “No SSL” — No certificate is installed for your domain. Go to the fix section.
  • Expired certificate — Your certificate has expired and needs renewal.

Step 2: Check Your DNS Records

Go to your domain registrar’s DNS management panel and confirm the records match exactly what Manus instructed you to add. Common settings Manus typically requires:

  • An A record pointing your root domain (@) to Manus’s IP address
  • A CNAME record pointing www to your Manus project URL

Cross-reference these with the DNS settings inside your Manus dashboard under Settings → Domains.

Step 3: Check DNS Propagation

Go to DNSChecker.org, enter your domain, and check whether your A record and CNAME are resolving correctly worldwide. If many locations are still showing old values, propagation is still in progress — wait longer.

Step 4: Check for Mixed Content

Open your site in Chrome. Right-click → Inspect → Console. Look for any errors or warnings mentioning “mixed content” or “blocked: mixed content.” These indicate specific assets loading over HTTP that need to be switched to HTTPS.

Step 5: Check Cloudflare Settings (If Applicable)

If you’re using Cloudflare, log in to your Cloudflare dashboard → select your domain → go to SSL/TLS. Check what SSL mode you have set. We’ll cover the correct setting below.

5. Step-by-Step SSL Fix for Manus Sites

Once you’ve diagnosed the problem, here’s how to fix the most common SSL issues with Manus-connected domains:

Fix 1: Wait for DNS Propagation and Let Manus Issue the Certificate

If your DNS records are correctly configured and you’ve recently made the change:

  1. Wait 24–48 hours for propagation to complete.
  2. Check your Manus dashboard under Settings → Domains to see if your domain shows a green SSL status.
  3. Once DNS propagates fully, Manus should automatically trigger SSL certificate issuance.
  4. If the Manus dashboard shows your domain as connected but still no SSL, try removing the domain and re-adding it to trigger a fresh certificate request.

Fix 2: Correct Your DNS Records

If your DNS records are wrong:

  1. Log in to your domain registrar (GoDaddy, Namecheap, Porkbun, Google Domains, etc.).
  2. Navigate to DNS Management for your domain.
  3. Open your Manus dashboard → Settings → Domains → click your connected domain to see the required DNS values.
  4. Delete any conflicting old A records or CNAMEs pointing to other services.
  5. Add the correct A record (type: A, host: @, value: Manus IP address).
  6. Add the correct CNAME record (type: CNAME, host: www, value: your Manus domain).
  7. Save and wait for propagation.
See also  What is OpenClaw? Your Open-Source AI Assistant for 2026

Fix 3: Force SSL Re-Issuance from Manus Dashboard

If your DNS is correctly configured but SSL still hasn’t been issued:

  1. Log in to Manus.
  2. Go to Settings → Domains.
  3. Remove your custom domain.
  4. Re-add the same custom domain.
  5. This forces Manus to attempt a fresh SSL certificate request for your domain.
  6. Wait up to 30 minutes for the certificate to be issued and installed.

Fix 4: Force HTTPS Redirect

Even with a valid SSL certificate, users might land on the HTTP version of your site. Ensure HTTPS is enforced:

  1. In your Manus dashboard, check if there’s an option to “Force HTTPS” or “Redirect HTTP to HTTPS” — enable it.
  2. If you’re using Cloudflare, enable Always Use HTTPS under SSL/TLS → Edge Certificates.

Fix 5: Fix Mixed Content Issues

If your SSL certificate is valid but you still see a broken padlock or warnings:

  1. Open Chrome DevTools (F12) → Console tab.
  2. Note all URLs flagged as mixed content (they’ll start with http://).
  3. Update those assets in your Manus site editor to use https:// URLs instead.
  4. If the HTTP URLs are from embedded third-party tools (maps, videos, etc.), check whether those services offer HTTPS embed codes and update accordingly.

6. The Cloudflare SSL Fix (If You Use Cloudflare)

If your domain’s DNS is managed through Cloudflare, this section is critical — Cloudflare’s SSL settings are one of the most common causes of the “Not Secure” issue on Manus sites.

Understanding Cloudflare’s SSL Modes

Cloudflare offers four SSL modes:

  • Off — No SSL at all. Never use this.
  • Flexible — Cloudflare encrypts traffic between the visitor and Cloudflare, but connects to your origin server (Manus) over plain HTTP. This causes SSL errors and redirect loops on Manus sites.
  • Full — Cloudflare encrypts traffic both ways but doesn’t validate the origin certificate. Works in most cases.
  • Full (Strict) — Cloudflare encrypts all traffic and validates the origin certificate. This is the most secure and recommended setting when Manus has issued a valid SSL certificate for your domain.

The Fix: Set Cloudflare to Full (Strict)

  1. Log in to Cloudflare.
  2. Select your domain from the dashboard.
  3. Click SSL/TLS in the left sidebar.
  4. Under “Your SSL/TLS encryption mode,” select Full (Strict).
  5. Scroll down and save.

If Manus’s SSL certificate hasn’t been issued yet, temporarily use Full (not Strict) until the Manus certificate is ready, then switch to Full (Strict).

Additional Cloudflare Settings to Enable

  • Always Use HTTPS — SSL/TLS → Edge Certificates → toggle on “Always Use HTTPS.”
  • Automatic HTTPS Rewrites — SSL/TLS → Edge Certificates → toggle on “Automatic HTTPS Rewrites.” This fixes most mixed content issues automatically.
  • HSTS — If you’re confident your SSL is stable, enable HTTP Strict Transport Security to tell browsers to always use HTTPS for your domain.

What If You’re Using Cloudflare Proxy (Orange Cloud)?

When the orange cloud icon is enabled next to your DNS record in Cloudflare, traffic is proxied through Cloudflare — meaning Cloudflare acts as a middleman between visitors and your Manus server. This can sometimes interfere with Manus’s SSL certificate issuance.

If SSL issuance is failing, try temporarily disabling the Cloudflare proxy (click the orange cloud to make it gray — “DNS Only” mode), wait for the Manus SSL certificate to be issued, then re-enable the proxy afterward.

7. Still Not Working? Advanced Troubleshooting

If you’ve waited 48 hours, verified your DNS, tried re-adding the domain, and your Manus site is still showing “Not Secure,” here are some advanced steps:

Check for CAA Records Blocking Certificate Issuance

CAA (Certification Authority Authorization) DNS records control which Certificate Authorities (CAs) are allowed to issue SSL certificates for your domain. If your domain has restrictive CAA records, they might be blocking Manus’s SSL provider from issuing a certificate.

Check your DNS for CAA records. If they exist and don’t include the CA that Manus uses (commonly Let’s Encrypt or DigiCert), add the appropriate CAA record or remove the restriction.

Check for Redirect Chains

Sometimes multiple redirects (e.g., domain → www → Manus → HTTPS) can create a redirect chain that results in SSL errors. Use a tool like httpstatus.io to trace every redirect your domain goes through and identify any unexpected hops.

See also  How AI is Revolutionizing Website Design in 2026

Clear Your Browser Cache and Test in Incognito

Your browser aggressively caches SSL states. Sometimes a site is properly secured, but your browser is showing a cached error. Always test in an incognito/private window, and try from a completely different device or network before concluding there’s still a problem.

Contact Manus Support

If you’ve exhausted all options, reach out to Manus support directly. Provide them with:

  • Your custom domain name
  • Screenshots of your DNS records
  • Your SSL Labs test report URL
  • The exact error message shown in your browser

The more specific your report, the faster they can identify whether the issue is on Manus’s infrastructure side.

8. How to Prevent This in Future Projects

Now that you’ve fixed the problem (or are in the process of fixing it), here are best practices to avoid the SSL headache on your next Manus project:

1. Set Up DNS First, Then Connect the Domain

Before connecting your domain inside Manus, go to your registrar and add the DNS records Manus requires. Wait until DNSChecker.org confirms propagation — then connect the domain in Manus. This gives Manus a clean signal to issue the certificate immediately.

2. Set Cloudflare SSL to Full (Strict) Before Connecting

If you use Cloudflare, configure the SSL mode to Full (Strict) before adding the domain to Manus. This prevents the Flexible SSL trap from day one.

3. Use Low TTL Before Making DNS Changes

Before changing your DNS records, lower your TTL (Time to Live) to 300 seconds (5 minutes). This means DNS changes propagate much faster, reducing your wait time from hours to minutes. Remember to raise the TTL back to normal (3600 seconds) afterward.

4. Monitor SSL Certificate Expiry

Use a free service like UptimeRobot or Certbot to monitor your SSL certificate’s expiry date and get email alerts before it expires. Most Manus-managed certificates auto-renew, but it’s worth monitoring independently.

5. Test SSL Immediately After Launch

Make SSL verification part of your launch checklist. After connecting a domain, immediately run an SSL Labs test and check all pages for mixed content before promoting the site to anyone.

10. Need Help? We Can Fix This For You

SSL configuration and domain setup can feel like navigating a minefield — especially when you just want to get your Manus site live and looking professional. If you’ve read through this guide and you’re still stuck, or if you simply don’t have time to troubleshoot it yourself, we can handle the entire setup for you.

Our team specializes in Manus site deployment, custom domain configuration, and SSL troubleshooting. We’ll:

  • ✅ Audit your current DNS configuration and identify the exact source of the SSL error
  • ✅ Correctly configure all DNS records at your registrar
  • ✅ Set up Cloudflare SSL correctly if you’re using it
  • ✅ Verify SSL issuance and force HTTPS across your entire Manus site
  • ✅ Fix any mixed content issues on your pages
  • ✅ Confirm your site shows a clean padlock on all major browsers
  • ✅ Provide a post-fix SSL monitoring setup so this doesn’t happen again

Stop losing visitors and credibility to a “Not Secure” warning. Reach out today and we’ll have your Manus site fully secured — usually within a few hours.

→ Contact Us to Fix Your Manus SSL Issue

Summary: Your Manus SSL Fix Checklist

Here’s a quick-reference checklist to bookmark:

  • ☐ Verify DNS records match Manus’s required settings exactly
  • ☐ Check DNS propagation on DNSChecker.org
  • ☐ Wait 24–48 hours before diagnosing a propagation issue
  • ☐ Run an SSL test on SSL Labs
  • ☐ If using Cloudflare: set SSL mode to Full (Strict)
  • ☐ Enable “Always Use HTTPS” and “Automatic HTTPS Rewrites” in Cloudflare
  • ☐ Remove and re-add your domain in Manus to trigger SSL re-issuance
  • ☐ Check for CAA records blocking certificate issuance
  • ☐ Fix any mixed content issues via Chrome DevTools console
  • ☐ Test in incognito mode and from multiple devices
  • ☐ Set up SSL expiry monitoring

Getting your Manus site properly secured is a one-time setup that pays dividends forever — in search rankings, visitor trust, and conversion rates. Take the time to get it right, and your site will be safe and professional for the long haul.

Found this guide helpful? Share it with anyone who’s just connected a custom domain to Manus and ran into the “Not Secure” problem — you might save them hours of frustration.