Home › Knowledgebase › KB-1254

Why is my secure website showing mixed content warnings?

Summary

This guide helps you troubleshoot and resolve: Why is my secure website showing mixed content warnings?. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Mixed content warnings occur when a website loads over a secure HTTPS connection but pulls certain resources—such as images, scripts, stylesheets, or fonts—over an insecure HTTP connection. Even with a valid SSL certificate installed, browsers flag these insecure elements to protect visitors, often displaying a “Not Secure” indicator or blocking the content entirely. This undermines visitor trust and can negatively impact your site’s search engine optimisation.

Quick Fix Steps

  1. Open your website in Google Chrome or Microsoft Edge.
  2. Press F12 to open Developer Tools.
  3. Click the Console tab.
  4. Look for messages marked Mixed Content that list insecure HTTP URLs.
  5. Update those resource references to use HTTPS.
  6. Clear your browser cache and reload the page to verify the warning is gone.

Detailed Instructions

Identify insecure resources

Modern browsers block or flag mixed content automatically. To find exactly which files are causing the warning:

  1. Visit your website using https://.
  2. Right-click anywhere on the page and select Inspect, or press F12.
  3. Open the Console tab in Developer Tools.
  4. Refresh the page.
  5. Review the list of warnings. Each entry will show the insecure URL being blocked or downgraded.

You can also check the Security tab in Chrome DevTools for a summary of the page’s secure and insecure origins.

Update CMS site URLs

If you use WordPress, mixed content is often caused by the site address configuration. Before updating individual resource links, verify your core site settings:

  1. Log in to your WordPress admin dashboard.
  2. Navigate to Settings > General.
  3. Check the WordPress Address (URL) field.
  4. Check the Site Address (URL) field.
  5. If either field begins with http://, update it to https://.
  6. Click Save Changes.
Changing these URLs may log you out of the WordPress dashboard. If this happens, simply log in again using the secure HTTPS address.

Update internal links and resource references

Once you have identified the insecure URLs, edit your website’s source files or content management system to replace http:// with https:// for:

Where possible, use protocol-relative URLs (for example, //example.com/image.jpg) so the browser automatically matches the page’s protocol.

If you use a content management system such as WordPress, a search-and-replace plugin can help update database references from HTTP to HTTPS across posts, pages, and media attachments.

Check external assets

Third-party resources such as embedded videos, analytics scripts, or advertising networks must also support HTTPS. If an external provider does not offer a secure version, contact them or replace the asset with a secure alternative.

Enforce HTTPS site-wide

After fixing mixed content, make sure all traffic is redirected to the secure version of your site. The exact steps depend on your hosting control panel:

cPanel

  1. Log in to cPanel.
  2. Navigate to the Security section.
  3. Select SSL/TLS Status or look for the Force HTTPS Redirect option.
  4. Toggle the redirect to On.
  5. Save the changes and test your website.

Plesk

  1. Log in to Plesk.
  2. Go to Websites & Domains.
  3. Select your domain and click Hosting Settings.
  4. Enable Permanent SEO-safe 301 redirect from HTTP to HTTPS.
  5. Click OK to apply the changes.

If your control panel does not include a built-in HTTPS redirect option, you can enforce HTTPS by adding a redirect rule to your website’s .htaccess file.

Do not hardcode http:// links in your theme or template files. Always use relative paths or https:// to prevent mixed content from returning after future updates.

Troubleshooting

Warning persists after updating links

Padlock still shows as insecure

Content blocked by browser

Some browsers actively block mixed content rather than just warning about it. If scripts or images fail to load entirely, updating every reference to HTTPS is required to restore functionality.

If you host with us and prefer not to manage 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