{"id":38710,"date":"2026-05-11T16:31:24","date_gmt":"2026-05-11T11:31:24","guid":{"rendered":"https:\/\/mcstarters.com\/blog\/?p=38710"},"modified":"2026-05-12T15:24:52","modified_gmt":"2026-05-12T10:24:52","slug":"why-your-manus-site-shows-not-secure-after-domain-connection-ssl-fix","status":"publish","type":"post","link":"https:\/\/mcstarters.com\/blog\/why-your-manus-site-shows-not-secure-after-domain-connection-ssl-fix\/","title":{"rendered":"Why Your Manus Site Shows &#8220;Not Secure&#8221; After Domain Connection (SSL Fix)"},"content":{"rendered":"\n<p><em>You spent hours building a beautiful site on Manus. You connected your custom domain, hit publish, typed your URL with excitement \u2014 and your browser slaps you with a red &#8220;Not Secure&#8221; warning. What went wrong?<\/em><\/p>\n\n\n\n<p>You&#8217;re not alone. The\u00a0<strong>&#8220;Not Secure&#8221; warning after connecting a custom domain to a Manus site<\/strong>\u00a0is one of the most common issues new Manus users face. The good news: it&#8217;s almost always an <a href=\"https:\/\/mcstarters.com\/blog\/free-ssl-certificate\/\" target=\"_blank\" data-type=\"link\" data-id=\"https:\/\/mcstarters.com\/blog\/free-ssl-certificate\/\" rel=\"noreferrer noopener\">SSL certificate<\/a> problem \u2014 and it&#8217;s completely fixable.<\/p>\n\n\n\n<p>In this guide, we&#8217;ll walk you through exactly&nbsp;<strong>why this happens, how to diagnose it, and how to fix the SSL error on your Manus-connected domain<\/strong>&nbsp;\u2014 step by step, without needing to be a technical expert.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><div><div><a href=\"#what-does-not-secure-mean\">1. What Does &#8220;Not Secure&#8221; Actually Mean?<\/a><\/div><div><a href=\"#why-manus-sites-show-this-warning\">2. Why Manus Sites Show This Warning After Domain Connection<\/a><\/div><div><a href=\"#dns-propagation\">3. The Role of DNS Propagation<\/a><\/div><div><a href=\"#how-to-diagnose\">4. How to Diagnose Your SSL Problem<\/a><\/div><div><a href=\"#step-by-step-fix\">5. Step-by-Step SSL Fix for Manus Sites<\/a><\/div><div><a href=\"#cloudflare-fix\">6. The Cloudflare SSL Fix (If You Use Cloudflare)<\/a><\/div><div><a href=\"#still-not-working\">7. Still Not Working? Advanced Troubleshooting<\/a><\/div><div><a href=\"#prevent-in-future\">8. How to Prevent This in Future Projects<\/a><\/div><div><a href=\"#need-help\">10. Need Help? We Can Fix This For You<\/a><\/div><div><a href=\"#summary-your-manus-ssl-fix-checklist\">Summary: Your Manus SSL Fix Checklist<\/a><\/div><\/div><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"what-does-not-secure-mean\">1. What Does &#8220;Not Secure&#8221; Actually Mean?<\/h2>\n\n\n\n<p>When your browser shows a &#8220;Not Secure&#8221; warning in the address bar, it means the website you&#8217;re visiting is being served over&nbsp;<strong>HTTP instead of HTTPS<\/strong>. The difference matters enormously:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>HTTP<\/strong>&nbsp;\u2014 Data travels between the browser and server in plain text. Anyone on the same network can intercept it.<\/li>\n\n\n\n<li><strong>HTTPS<\/strong>&nbsp;\u2014 Data is encrypted using an SSL\/TLS certificate. It&#8217;s secure, private, and trusted by browsers.<\/li>\n<\/ul>\n\n\n\n<p class=\"bg-light\"><a href=\"https:\/\/mcstarters.com\/blog\/free-ssl-certificate\/\" target=\"_blank\" data-type=\"post\" data-id=\"35919\" rel=\"noreferrer noopener\">Getting a free SSL certificate for your website using Cloudflare<\/a><\/p>\n\n\n\n<p>An&nbsp;<strong>SSL certificate<\/strong>&nbsp;(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 &#8220;Not Secure&#8221; warning \u2014 even if the site itself looks and works perfectly.<\/p>\n\n\n\n<p>This isn&#8217;t just a cosmetic issue. Here&#8217;s why it matters:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Visitors distrust it immediately<\/strong>&nbsp;\u2014 Most users will leave a site the moment they see the warning.<\/li>\n\n\n\n<li><strong>Google penalizes non-HTTPS sites<\/strong>&nbsp;\u2014 It&#8217;s a confirmed ranking signal. HTTP sites rank lower.<\/li>\n\n\n\n<li><strong>Browsers actively block some content<\/strong>&nbsp;\u2014 Chrome, Firefox, and Safari increasingly block non-secure sites from loading certain features.<\/li>\n\n\n\n<li><strong>Forms and payments are at risk<\/strong>&nbsp;\u2014 Any contact form, checkout, or login on an HTTP site is a liability.<\/li>\n<\/ul>\n\n\n\n<p>The bottom line:&nbsp;<strong>a &#8220;Not Secure&#8221; warning is a showstopper<\/strong>, and it needs to be fixed before you promote your Manus site to anyone.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"why-manus-sites-show-this-warning\">2. Why Manus Sites Show This Warning After Domain Connection<\/h2>\n\n\n\n<p>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.,&nbsp;<code>yoursite.manus.app<\/code>), SSL is handled automatically \u2014 everything is secure out of the box.<\/p>\n\n\n\n<p>The problem almost always appears the moment you&nbsp;<strong>connect a custom domain<\/strong>&nbsp;(e.g.,&nbsp;<code>www.yourbusiness.com<\/code>).<\/p>\n\n\n\n<p>Here&#8217;s why:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"reason-1-the-ssl-certificate-hasnt-been-issued-yet-for-your-domain\">Reason 1: The SSL Certificate Hasn&#8217;t Been Issued Yet for Your Domain<\/h3>\n\n\n\n<p>When you connect a custom domain to Manus, the platform needs to issue a new SSL certificate specifically for&nbsp;<em>your<\/em>&nbsp;domain. This is different from the certificate that covers the&nbsp;<code>manus.app<\/code>&nbsp;subdomain you used during building.<\/p>\n\n\n\n<p>Manus typically uses an automated SSL provider (like Let&#8217;s Encrypt or similar) to generate and install this certificate. But this process isn&#8217;t instantaneous \u2014 it requires your domain&#8217;s DNS records to fully propagate and point correctly to Manus&#8217;s servers before the certificate can be validated and issued.<\/p>\n\n\n\n<p>If you visit your custom domain too soon, the certificate may not be ready yet, resulting in the &#8220;Not Secure&#8221; warning.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"reason-2-dns-records-are-configured-incorrectly\">Reason 2: DNS Records Are Configured Incorrectly<\/h3>\n\n\n\n<p>For Manus to issue an SSL certificate for your domain, your domain&#8217;s DNS settings must point to Manus&#8217;s servers. Common DNS configuration mistakes include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pointing only the root domain (<code>yourdomain.com<\/code>) but forgetting the&nbsp;<code>www<\/code>&nbsp;subdomain (or vice versa)<\/li>\n\n\n\n<li>Adding a CNAME record where an A record is required<\/li>\n\n\n\n<li>Leaving old DNS records that conflict with the new Manus settings<\/li>\n\n\n\n<li>Entering the Manus IP or CNAME value with a typo<\/li>\n<\/ul>\n\n\n\n<p>When DNS is misconfigured, Manus can&#8217;t complete the SSL verification process, and your site stays insecure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"reason-3-cloudflares-ssl-mode-is-set-incorrectly\">Reason 3: Cloudflare&#8217;s SSL Mode Is Set Incorrectly<\/h3>\n\n\n\n<p>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&#8217;t set correctly, it creates a conflict that causes SSL errors \u2014 even if both Cloudflare and Manus technically have certificates.<\/p>\n\n\n\n<p>The most dangerous setting here is&nbsp;<strong>Flexible SSL<\/strong>, which we&#8217;ll cover in detail later.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"reason-4-mixed-content-issues\">Reason 4: Mixed Content Issues<\/h3>\n\n\n\n<p>Sometimes your domain and SSL certificate are fine \u2014 but specific pages or elements on your site load resources (images, scripts, stylesheets) over HTTP instead of HTTPS. This is called a&nbsp;<strong>mixed content error<\/strong>&nbsp;and will still trigger a &#8220;Not Secure&#8221; warning or a broken padlock icon even with a valid SSL certificate.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"reason-5-ssl-certificate-has-expired\">Reason 5: SSL Certificate Has Expired<\/h3>\n\n\n\n<p>SSL certificates aren&#8217;t permanent. They typically expire every 90 days (for free Let&#8217;s Encrypt certificates) or every 1\u20132 years (for paid certificates). If auto-renewal fails, your site will suddenly show as &#8220;Not Secure&#8221; even though it was previously secure.<\/p>\n\n\n\n<p><a href=\"https:\/\/mcstarters.com\/blog\/free-ssl-certificate\/\" data-type=\"post\" data-id=\"35919\" target=\"_blank\" rel=\"noreferrer noopener\">Getting a free SSL certificate for your website using Cloudflare<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"dns-propagation\">3. The Role of DNS Propagation<\/h2>\n\n\n\n<p>Before we get into the fix, it&#8217;s important to understand DNS propagation \u2014 because rushing this step is the #1 cause of confusion and frustration.<\/p>\n\n\n\n<p><strong>DNS propagation<\/strong>&nbsp;is the time it takes for changes to your domain&#8217;s DNS settings to spread across all DNS servers worldwide. When you update your DNS records to point to Manus, that change doesn&#8217;t happen instantly everywhere on the internet.<\/p>\n\n\n\n<p>Propagation can take anywhere from&nbsp;<strong>a few minutes to 48 hours<\/strong>, depending on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your domain registrar (GoDaddy, <a  class=\"btl_autolink_hyperlink\"  href=\"https:\/\/mcstarters.com\/blog\/namecheap\"    target=\"_blank\" rel=\"nofollow\">Namecheap<\/a>, Google Domains, etc.)<\/li>\n\n\n\n<li>Your TTL (Time to Live) settings \u2014 how long DNS servers cache your old records<\/li>\n\n\n\n<li>Your ISP and geographic location<\/li>\n<\/ul>\n\n\n\n<p>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 \u2014 or an SSL error.<\/p>\n\n\n\n<p><strong>What to do:<\/strong>&nbsp;After making DNS changes, wait at least&nbsp;<strong>24 hours<\/strong>&nbsp;before diagnosing a problem. Use a tool like&nbsp;<a href=\"https:\/\/dnschecker.org\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">DNSChecker.org<\/a>&nbsp;to see whether your DNS has propagated globally before troubleshooting further.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"how-to-diagnose\">4. How to Diagnose Your SSL Problem<\/h2>\n\n\n\n<p>Before jumping to fixes, let&#8217;s figure out exactly what&#8217;s going wrong. Here&#8217;s a quick diagnostic checklist:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-1-check-your-ssl-certificate-status\">Step 1: Check Your SSL Certificate Status<\/h3>\n\n\n\n<p>Visit&nbsp;<a href=\"https:\/\/www.ssllabs.com\/ssltest\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">SSL Labs&#8217; SSL Test<\/a>&nbsp;and enter your domain. This free tool will give you a full report on your SSL certificate \u2014 whether it exists, who issued it, when it expires, and any errors.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Grade A or B<\/strong>&nbsp;\u2014 SSL is working. Your issue might be mixed content (see Step 4).<\/li>\n\n\n\n<li><strong>&#8220;No SSL&#8221;<\/strong>&nbsp;\u2014 No certificate is installed for your domain. Go to the fix section.<\/li>\n\n\n\n<li><strong>Expired certificate<\/strong>&nbsp;\u2014 Your certificate has expired and needs renewal.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-2-check-your-dns-records\">Step 2: Check Your DNS Records<\/h3>\n\n\n\n<p>Go to your domain registrar&#8217;s DNS management panel and confirm the records match exactly what Manus instructed you to add. Common settings Manus typically requires:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An&nbsp;<strong>A record<\/strong>&nbsp;pointing your root domain (<code>@<\/code>) to Manus&#8217;s IP address<\/li>\n\n\n\n<li>A&nbsp;<strong>CNAME record<\/strong>&nbsp;pointing&nbsp;<code>www<\/code>&nbsp;to your Manus project URL<\/li>\n<\/ul>\n\n\n\n<p>Cross-reference these with the DNS settings inside your Manus dashboard under&nbsp;<em>Settings \u2192 Domains<\/em>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-3-check-dns-propagation\">Step 3: Check DNS Propagation<\/h3>\n\n\n\n<p>Go to&nbsp;<a href=\"https:\/\/dnschecker.org\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">DNSChecker.org<\/a>, 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 \u2014 wait longer.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-4-check-for-mixed-content\">Step 4: Check for Mixed Content<\/h3>\n\n\n\n<p>Open your site in Chrome. Right-click \u2192 Inspect \u2192 Console. Look for any errors or warnings mentioning &#8220;mixed content&#8221; or &#8220;blocked: mixed content.&#8221; These indicate specific assets loading over HTTP that need to be switched to HTTPS.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-5-check-cloudflare-settings-if-applicable\">Step 5: Check Cloudflare Settings (If Applicable)<\/h3>\n\n\n\n<p>If you&#8217;re using Cloudflare, log in to your Cloudflare dashboard \u2192 select your domain \u2192 go to&nbsp;<em>SSL\/TLS<\/em>. Check what SSL mode you have set. We&#8217;ll cover the correct setting below.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"step-by-step-fix\">5. Step-by-Step SSL Fix for Manus Sites<\/h2>\n\n\n\n<p>Once you&#8217;ve diagnosed the problem, here&#8217;s how to fix the most common SSL issues with Manus-connected domains:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"fix-1-wait-for-dns-propagation-and-let-manus-issue-the-certificate\">Fix 1: Wait for DNS Propagation and Let Manus Issue the Certificate<\/h3>\n\n\n\n<p>If your DNS records are correctly configured and you&#8217;ve recently made the change:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Wait 24\u201348 hours for propagation to complete.<\/li>\n\n\n\n<li>Check your Manus dashboard under&nbsp;<em>Settings \u2192 Domains<\/em>&nbsp;to see if your domain shows a green SSL status.<\/li>\n\n\n\n<li>Once DNS propagates fully, Manus should automatically trigger SSL certificate issuance.<\/li>\n\n\n\n<li>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.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"fix-2-correct-your-dns-records\">Fix 2: Correct Your DNS Records<\/h3>\n\n\n\n<p>If your DNS records are wrong:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Log in to your domain registrar (GoDaddy, <a  class=\"btl_autolink_hyperlink\"  href=\"https:\/\/mcstarters.com\/blog\/namecheap\"    target=\"_blank\" rel=\"nofollow\">Namecheap<\/a>, Porkbun, Google Domains, etc.).<\/li>\n\n\n\n<li>Navigate to DNS Management for your domain.<\/li>\n\n\n\n<li>Open your Manus dashboard \u2192&nbsp;<em>Settings \u2192 Domains<\/em>&nbsp;\u2192 click your connected domain to see the required DNS values.<\/li>\n\n\n\n<li>Delete any conflicting old A records or CNAMEs pointing to other services.<\/li>\n\n\n\n<li>Add the correct A record (type: A, host: @, value: Manus IP address).<\/li>\n\n\n\n<li>Add the correct CNAME record (type: CNAME, host: www, value: your Manus domain).<\/li>\n\n\n\n<li>Save and wait for propagation.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"fix-3-force-ssl-re-issuance-from-manus-dashboard\">Fix 3: Force SSL Re-Issuance from Manus Dashboard<\/h3>\n\n\n\n<p>If your DNS is correctly configured but SSL still hasn&#8217;t been issued:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Log in to Manus.<\/li>\n\n\n\n<li>Go to&nbsp;<em>Settings \u2192 Domains<\/em>.<\/li>\n\n\n\n<li>Remove your custom domain.<\/li>\n\n\n\n<li>Re-add the same custom domain.<\/li>\n\n\n\n<li>This forces Manus to attempt a fresh SSL certificate request for your domain.<\/li>\n\n\n\n<li>Wait up to 30 minutes for the certificate to be issued and installed.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"fix-4-force-https-redirect\">Fix 4: Force HTTPS Redirect<\/h3>\n\n\n\n<p>Even with a valid SSL certificate, users might land on the HTTP version of your site. Ensure HTTPS is enforced:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In your Manus dashboard, check if there&#8217;s an option to &#8220;Force HTTPS&#8221; or &#8220;Redirect HTTP to HTTPS&#8221; \u2014 enable it.<\/li>\n\n\n\n<li>If you&#8217;re using Cloudflare, enable&nbsp;<em>Always Use HTTPS<\/em>&nbsp;under SSL\/TLS \u2192 Edge Certificates.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"fix-5-fix-mixed-content-issues\">Fix 5: Fix Mixed Content Issues<\/h3>\n\n\n\n<p>If your SSL certificate is valid but you still see a broken padlock or warnings:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open Chrome DevTools (F12) \u2192 Console tab.<\/li>\n\n\n\n<li>Note all URLs flagged as mixed content (they&#8217;ll start with&nbsp;<code>http:\/\/<\/code>).<\/li>\n\n\n\n<li>Update those assets in your Manus site editor to use&nbsp;<code>https:\/\/<\/code>&nbsp;URLs instead.<\/li>\n\n\n\n<li>If the HTTP URLs are from embedded third-party tools (maps, videos, etc.), check whether those services offer HTTPS embed codes and update accordingly.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"cloudflare-fix\">6. The Cloudflare SSL Fix (If You Use Cloudflare)<\/h2>\n\n\n\n<p>If your domain&#8217;s DNS is managed through Cloudflare, this section is critical \u2014 Cloudflare&#8217;s SSL settings are one of the most common causes of the &#8220;Not Secure&#8221; issue on Manus sites.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"understanding-cloudflares-ssl-modes\">Understanding Cloudflare&#8217;s SSL Modes<\/h3>\n\n\n\n<p>Cloudflare offers four SSL modes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Off<\/strong>&nbsp;\u2014 No SSL at all. Never use this.<\/li>\n\n\n\n<li><strong>Flexible<\/strong>&nbsp;\u2014 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.<\/li>\n\n\n\n<li><strong>Full<\/strong>&nbsp;\u2014 Cloudflare encrypts traffic both ways but doesn&#8217;t validate the origin certificate. Works in most cases.<\/li>\n\n\n\n<li><strong>Full (Strict)<\/strong>&nbsp;\u2014 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.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"the-fix-set-cloudflare-to-full-strict\">The Fix: Set Cloudflare to Full (Strict)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Log in to&nbsp;<a href=\"https:\/\/cloudflare.com\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Cloudflare<\/a>.<\/li>\n\n\n\n<li>Select your domain from the dashboard.<\/li>\n\n\n\n<li>Click&nbsp;<strong>SSL\/TLS<\/strong>&nbsp;in the left sidebar.<\/li>\n\n\n\n<li>Under &#8220;Your SSL\/TLS encryption mode,&#8221; select&nbsp;<strong>Full (Strict)<\/strong>.<\/li>\n\n\n\n<li>Scroll down and save.<\/li>\n<\/ol>\n\n\n\n<p>If Manus&#8217;s SSL certificate hasn&#8217;t been issued yet, temporarily use&nbsp;<strong>Full<\/strong>&nbsp;(not Strict) until the Manus certificate is ready, then switch to Full (Strict).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"additional-cloudflare-settings-to-enable\">Additional Cloudflare Settings to Enable<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Always Use HTTPS<\/strong>&nbsp;\u2014 SSL\/TLS \u2192 Edge Certificates \u2192 toggle on &#8220;Always Use HTTPS.&#8221;<\/li>\n\n\n\n<li><strong>Automatic HTTPS Rewrites<\/strong>&nbsp;\u2014 SSL\/TLS \u2192 Edge Certificates \u2192 toggle on &#8220;Automatic HTTPS Rewrites.&#8221; This fixes most mixed content issues automatically.<\/li>\n\n\n\n<li><strong>HSTS<\/strong>&nbsp;\u2014 If you&#8217;re confident your SSL is stable, enable HTTP Strict Transport Security to tell browsers to always use HTTPS for your domain.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"what-if-youre-using-cloudflare-proxy-orange-cloud\">What If You&#8217;re Using Cloudflare Proxy (Orange Cloud)?<\/h3>\n\n\n\n<p>When the orange cloud icon is enabled next to your DNS record in Cloudflare, traffic is proxied through Cloudflare \u2014 meaning Cloudflare acts as a middleman between visitors and your Manus server. This can sometimes interfere with Manus&#8217;s SSL certificate issuance.<\/p>\n\n\n\n<p>If SSL issuance is failing, try temporarily&nbsp;<strong>disabling the Cloudflare proxy<\/strong>&nbsp;(click the orange cloud to make it gray \u2014 &#8220;DNS Only&#8221; mode), wait for the Manus SSL certificate to be issued, then re-enable the proxy afterward.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"still-not-working\">7. Still Not Working? Advanced Troubleshooting<\/h2>\n\n\n\n<p>If you&#8217;ve waited 48 hours, verified your DNS, tried re-adding the domain, and your Manus site is still showing &#8220;Not Secure,&#8221; here are some advanced steps:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"check-for-caa-records-blocking-certificate-issuance\">Check for CAA Records Blocking Certificate Issuance<\/h3>\n\n\n\n<p>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&#8217;s SSL provider from issuing a certificate.<\/p>\n\n\n\n<p>Check your DNS for CAA records. If they exist and don&#8217;t include the CA that Manus uses (commonly Let&#8217;s Encrypt or DigiCert), add the appropriate CAA record or remove the restriction.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"check-for-redirect-chains\">Check for Redirect Chains<\/h3>\n\n\n\n<p>Sometimes multiple redirects (e.g., domain \u2192 www \u2192 Manus \u2192 HTTPS) can create a redirect chain that results in SSL errors. Use a tool like&nbsp;<a href=\"https:\/\/httpstatus.io\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">httpstatus.io<\/a>&nbsp;to trace every redirect your domain goes through and identify any unexpected hops.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"clear-your-browser-cache-and-test-in-incognito\">Clear Your Browser Cache and Test in Incognito<\/h3>\n\n\n\n<p>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&#8217;s still a problem.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"contact-manus-support\">Contact Manus Support<\/h3>\n\n\n\n<p>If you&#8217;ve exhausted all options, reach out to Manus support directly. Provide them with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your custom domain name<\/li>\n\n\n\n<li>Screenshots of your DNS records<\/li>\n\n\n\n<li>Your SSL Labs test report URL<\/li>\n\n\n\n<li>The exact error message shown in your browser<\/li>\n<\/ul>\n\n\n\n<p>The more specific your report, the faster they can identify whether the issue is on Manus&#8217;s infrastructure side.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"prevent-in-future\">8. How to Prevent This in Future Projects<\/h2>\n\n\n\n<p>Now that you&#8217;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:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1-set-up-dns-first-then-connect-the-domain\">1. Set Up DNS First, Then Connect the Domain<\/h3>\n\n\n\n<p>Before connecting your domain inside Manus, go to your registrar and add the DNS records Manus requires. Wait until DNSChecker.org confirms propagation \u2014 then connect the domain in Manus. This gives Manus a clean signal to issue the certificate immediately.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2-set-cloudflare-ssl-to-full-strict-before-connecting\">2. Set Cloudflare SSL to Full (Strict) Before Connecting<\/h3>\n\n\n\n<p>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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-use-low-ttl-before-making-dns-changes\">3. Use Low TTL Before Making DNS Changes<\/h3>\n\n\n\n<p>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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"4-monitor-ssl-certificate-expiry\">4. Monitor SSL Certificate Expiry<\/h3>\n\n\n\n<p>Use a free service like&nbsp;<a href=\"https:\/\/uptimerobot.com\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">UptimeRobot<\/a>&nbsp;or&nbsp;<a href=\"https:\/\/certbot.eff.org\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Certbot<\/a>&nbsp;to monitor your SSL certificate&#8217;s expiry date and get email alerts before it expires. Most Manus-managed certificates auto-renew, but it&#8217;s worth monitoring independently.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"5-test-ssl-immediately-after-launch\">5. Test SSL Immediately After Launch<\/h3>\n\n\n\n<p>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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"need-help\">10. Need Help? We Can Fix This For You<\/h2>\n\n\n\n<p>SSL configuration and domain setup can feel like navigating a minefield \u2014 especially when you just want to get your Manus site live and looking professional. If you&#8217;ve read through this guide and you&#8217;re still stuck, or if you simply don&#8217;t have time to troubleshoot it yourself,&nbsp;<strong>we can handle the entire setup for you.<\/strong><\/p>\n\n\n\n<p>Our team specializes in Manus site deployment, custom domain configuration, and SSL troubleshooting. We&#8217;ll:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u2705 Audit your current DNS configuration and identify the exact source of the SSL error<\/li>\n\n\n\n<li>\u2705 Correctly configure all DNS records at your registrar<\/li>\n\n\n\n<li>\u2705 Set up Cloudflare SSL correctly if you&#8217;re using it<\/li>\n\n\n\n<li>\u2705 Verify SSL issuance and force HTTPS across your entire Manus site<\/li>\n\n\n\n<li>\u2705 Fix any mixed content issues on your pages<\/li>\n\n\n\n<li>\u2705 Confirm your site shows a clean padlock on all major browsers<\/li>\n\n\n\n<li>\u2705 Provide a post-fix SSL monitoring setup so this doesn&#8217;t happen again<\/li>\n<\/ul>\n\n\n\n<p><strong>Stop losing visitors and credibility to a &#8220;Not Secure&#8221; warning.<\/strong>&nbsp;Reach out today and we&#8217;ll have your Manus site fully secured \u2014 usually within a few hours.<\/p>\n\n\n\n<p><a href=\"https:\/\/mudassar.work\/\" data-type=\"link\" data-id=\"https:\/\/mudassar.work\/\" target=\"_blank\" rel=\"noopener\"><strong>\u2192 Contact Us to Fix Your Manus SSL Issue<\/strong><\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"summary-your-manus-ssl-fix-checklist\">Summary: Your Manus SSL Fix Checklist<\/h2>\n\n\n\n<p>Here&#8217;s a quick-reference checklist to bookmark:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u2610 Verify DNS records match Manus&#8217;s required settings exactly<\/li>\n\n\n\n<li>\u2610 Check DNS propagation on DNSChecker.org<\/li>\n\n\n\n<li>\u2610 Wait 24\u201348 hours before diagnosing a propagation issue<\/li>\n\n\n\n<li>\u2610 Run an SSL test on SSL Labs<\/li>\n\n\n\n<li>\u2610 If using Cloudflare: set SSL mode to Full (Strict)<\/li>\n\n\n\n<li>\u2610 Enable &#8220;Always Use HTTPS&#8221; and &#8220;Automatic HTTPS Rewrites&#8221; in Cloudflare<\/li>\n\n\n\n<li>\u2610 Remove and re-add your domain in Manus to trigger SSL re-issuance<\/li>\n\n\n\n<li>\u2610 Check for CAA records blocking certificate issuance<\/li>\n\n\n\n<li>\u2610 Fix any mixed content issues via Chrome DevTools console<\/li>\n\n\n\n<li>\u2610 Test in incognito mode and from multiple devices<\/li>\n\n\n\n<li>\u2610 Set up SSL expiry monitoring<\/li>\n<\/ul>\n\n\n\n<p>Getting your Manus site properly secured is a one-time setup that pays dividends forever \u2014 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.<\/p>\n\n\n\n<p><em>Found this guide helpful? Share it with anyone who&#8217;s just connected a custom domain to Manus and ran into the &#8220;Not Secure&#8221; problem \u2014 you might save them hours of frustration.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>You spent hours building a beautiful site on Manus. You&#8230;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[902,277],"tags":[],"class_list":["post-38710","post","type-post","status-publish","format-standard","hentry","category-manus-ai","category-ai"],"_links":{"self":[{"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/posts\/38710","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/comments?post=38710"}],"version-history":[{"count":2,"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/posts\/38710\/revisions"}],"predecessor-version":[{"id":38738,"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/posts\/38710\/revisions\/38738"}],"wp:attachment":[{"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/media?parent=38710"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/categories?post=38710"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mcstarters.com\/blog\/wp-json\/wp\/v2\/tags?post=38710"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}