Skip to main content
Submit a request

My SSL or HTTPS isn't working

Maxim Tsitsejev
Updated

Applies to: All plans.

Most SSL and HTTPS problems come down to one of three things: the certificate hasn't issued yet, it has expired or needs reissuing, or your site still loads some content over insecure http://. This article helps you spot which one you have and sends you to the exact fix.

We issue a free AutoSSL (Let's Encrypt) certificate automatically for every domain and renew it before it expires, so most sites stay secure with nothing to do.

Symptoms

  • The browser shows Not Secure, a crossed-out padlock, or a "Your connection is not private" warning.
  • https:// won't load at all, but http:// does.
  • The padlock is there but the site looks broken — some images, styles or scripts don't load.
  • The certificate covers your main domain but not www, or covers www but not the main domain.
  • A browser warning says the certificate has expired or the name does not match.

Common causes (most likely first)

  1. Mixed content — the certificate is fine, but your pages hard-code http:// links for images, CSS or scripts. The browser shows a warning even though HTTPS works.
  2. AutoSSL hasn't issued yet — on a brand-new domain or one that just pointed to us, the certificate can take a short while to be issued.
  3. DNS isn't pointing at us — AutoSSL can only secure a domain that already resolves to your hosting. If your nameservers or DNS aren't set, the certificate never issues.
  4. The certificate expired or needs reissuing — rare, since AutoSSL auto-renews, but it can happen after a domain change or if validation failed.
  5. A name isn't covered — the certificate is missing www, a subdomain, or an addon domain.

Quick fixes — find your symptom

The padlock warning is "Not secure" or content is mixed (HTTPS works, but the page looks broken or warns): This is mixed content — hard-coded http:// links on your pages. See Why does my site show 'Not Secure' or mixed content?.

No certificate, an expired certificate, a name-mismatch error, or www/a subdomain not covered: Check the certificate's status and reissue it if needed. See How to check or reissue your SSL certificate.

You're not sure HTTPS is even being used, or you want visitors forced to the secure version: Learn how free SSL works and how to force HTTPS. See Free SSL (AutoSSL) and how to force HTTPS.

Result: Once your domain resolves to us and AutoSSL has issued, your site loads over https:// with a valid padlock and no warnings.

If that did not work

  • Confirm your domain points to us first. AutoSSL cannot secure a domain that doesn't resolve to your hosting. Your nameservers should be ns1.maxinodes.com and ns2.maxinodes.com, and your main records should point to 185.185.49.198. You manage these records in your client area, not the cPanel zone editor. If DNS isn't resolving, fix that first — see My domain or DNS isn't resolving.
  • Give a new domain a little time. If you've only just pointed the domain or set nameservers, allow for DNS propagation (usually minutes to a few hours, up to 24–48 hours in the worst case) before the certificate can issue.
  • Still stuck? Start a chat and tell us your domain, the exact warning text, and whether http:// loads. We can check AutoSSL and reissue from our side.

Related articles

Comments

0 comments

Please sign in to leave a comment.