Launch mistakes

Mixed content and SSL errors on a new site

Mixed content is an HTTPS page that loads images, scripts, stylesheets or other files over plain HTTP; an SSL error means the browser does not trust the site's certificate. Browsers block many insecure files and warn visitors before opening a site with an untrusted certificate, so after launch people see broken pages or a security warning instead of the site. Check the certificate and the browser console on the live domain as soon as DNS points at the new server.

Last reviewed

← All launch mistakes

MDN defines mixed content as securely loaded pages that fetch resources over HTTP or another insecure protocol. Browsers upgrade some of these requests, such as images, to HTTPS and block the others. (Source: MDN: Mixed content)

How it happens

Content written on a staging server without a certificate stores image and file URLs that start with http://. Theme settings, page builder blocks and hard-coded embeds keep those URLs after the site moves to HTTPS.

Certificate problems usually come with the DNS switch: the certificate was issued for the staging hostname or for only one of the www and non-www names, the chain is incomplete, or the certificate has not been issued yet when traffic arrives.

How to spot it yourself

  1. Open the live site, click the site information icon next to the address and view the certificate and the names it covers. Try both the www and the non-www address.
  2. Open the developer tools' Console and reload. Mixed-content warnings and blocked requests are listed there.
  3. Type the http:// address of the site and confirm it redirects to https://.
  4. From a terminal, curl -vI with the https:// address prints the certificate verification result.

How to fix it

  • Install a valid certificate that covers every hostname the site answers on, with the full chain.
  • Redirect all HTTP requests to HTTPS at the server or hosting level.
  • Update stored http:// URLs in content and settings to https:// or relative paths, and switch embeds to their HTTPS address.

What Launch Ready checks

Each finding below shows the title, “Why it matters” and “How to fix” text the report uses. Severities are the defaults; a project rule override can change or silence a rule.

Rule ssl_failure

What the scan looks at: Runs when the scanned address starts with https://. It opens a TLS connection to that host and reports the site when the certificate is not trusted, with the connection's error as evidence.

Default severity: Block Launch.

SSL certificate is not trusted

Why it matters: Browsers will warn visitors that the connection is not secure. Do not launch on a broken certificate.

How to fix: Install a valid certificate (e.g. Let's Encrypt) and confirm the full chain in an SSL checker.

Rule http_on_https

What the scan looks at: Runs when the scanned address starts with https:// and reports each crawled page whose final address, after redirects, is still http://.

Default severity: Important.

HTTP page on an HTTPS site

Why it matters: Part of the site is still served over HTTP, which triggers mixed-content and trust warnings.

How to fix: Force HTTPS at the host and update internal links to https://.

Rule mixed_content

What the scan looks at: On each crawled HTTPS page, reads the markup, and the rendered page where there is one, for files loaded over http://: any src attribute; stylesheet, icon, manifest and preload links; <object data>; and video posters. A plain link to an http:// page loads nothing and is not reported.

Default severity: Important.

Insecure file on a secure page (mixed content)

Why it matters: This HTTPS page loads a resource over HTTP. Modern browsers will block it, breaking images or scripts.

How to fix: Serve the asset over HTTPS or update the reference.

What Launch Ready does not check here

  • Certificate expiry ahead of time. The check reports a certificate that is not trusted when the scan runs, not one that expires soon.
  • Certificates on hostnames other than the scanned one, such as the www or non-www variant.
  • Insecure files referenced from inside CSS files, or requested by scripts without appearing in the page.
  • TLS configuration such as protocol versions and ciphers. Launch Ready is not a security test.
  • Launch Ready does not guarantee a bug-free website.
  • It does not make the launch decision. People make it, with the report in hand.

How we scan describes what the crawler fetches, renders and stores.

Related checklist items

From the free 72-item website launch checklist, with each item's coverage label: Scan check, Partly checked or Manual.

Check your next client site before handoff

Add the staging or live URL, read the fix list, and send the client a report when it is ready.

Create a Launch Ready account to run a scan.