Home › Knowledgebase › KB-1378

Why Is My Website Showing Mixed Content Errors And How Do I Fix Https?

Summary

This guide helps you troubleshoot and resolve: Why Is My Website Showing Mixed Content Errors And How Do I Fix Https?. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Mixed content occurs when a website loads over a secure HTTPS connection but pulls certain resources, such as images, stylesheets, or scripts, over an unsecured HTTP connection. Modern browsers often block these insecure elements, which can result in missing imagery, broken page layouts, or security warnings that reduce visitor trust. This article explains how mixed content errors occur, the impact on site security and SEO, and the general steps required to identify and update insecure resource URLs so that all assets are served over HTTPS.

Quick Fix Steps

  1. Open your website in Google Chrome, Microsoft Edge, or Mozilla Firefox.
  2. Press F12 to open Developer Tools and select the Console tab.
  3. Refresh the page and look for warnings containing Mixed Content or Blocked.
  4. Note the insecure URLs listed (they will begin with http://).
  5. Update those URLs in your website code or content management system to use https://.
  6. Clear your browser cache and refresh the page to confirm the warnings are gone.

Detailed Instructions

Identify Mixed Content Errors

  1. Visit your website using https:// in your browser.
  2. Look for the padlock icon in the address bar. If it shows a warning triangle or says "Not secure," mixed content is likely present.
  3. Right-click anywhere on the page and select Inspect or press F12.
  4. Click the Console tab in Developer Tools.
  5. Refresh the page using F5 or Ctrl + R (Windows) / Cmd + R (Mac).
  6. Review the list of errors. Mixed content warnings typically read: Mixed Content: The page at '...' was loaded over HTTPS, but requested an insecure resource 'http://...'.

Update Insecure Resource URLs

  1. Open your website files using an FTP client, file manager, or your content management system.
  2. Search your HTML, CSS, JavaScript, and template files for instances of http://.
  3. Change internal resource links from http:// to https://. For example:
    • <img src="http://yourdomain.com.au/image.jpg"> becomes <img src="https://yourdomain.com.au/image.jpg">
    • <link rel="stylesheet" href="http://yourdomain.com.au/style.css"> becomes <link rel="stylesheet" href="https://yourdomain.com.au/style.css">
  4. If you use a CMS such as WordPress, update the WordPress Address (URL) and Site Address (URL) under Settings > General to use https://.
  5. Save your changes and upload the modified files if necessary.

Force HTTPS Redirects

  1. Access your website's .htaccess file via FTP or file manager (Apache servers).
  2. Add a redirect rule to send all HTTP traffic to HTTPS.
  3. Save the file and test your website by visiting http://yourdomain.com.au — it should automatically redirect to https://yourdomain.com.au.
  4. If you use a different web server (such as Nginx), configure the redirect in your server block or hosting control panel.

Troubleshooting

Warnings Persist After Updating URLs

Third-Party Resources Load Over HTTP

SSL Certificate Issues

Do not edit core website files without creating a backup first. Incorrect changes to .htaccess or theme files can take your website offline.

Resolving mixed content errors ensures that every element on your page is delivered securely, protects visitor data, and helps maintain trust and search engine visibility. If you are unable to locate or fix the insecure resources, Open a Ticket for assistance.

Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket