Home › Knowledgebase › KB-1276

Why are some images not loading on my website after installing an ssl certificate

Summary

This guide helps you troubleshoot and resolve: Why are some images not loading on my website after installing an ssl certificate. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

After installing an SSL certificate and forcing your website to load over HTTPS, you may notice that certain images, stylesheets, or scripts fail to appear. Browsers might also display a "Not Secure" warning or a broken padlock icon in the address bar. This happens because some elements on your pages are still being requested over an unsecured HTTP connection rather than HTTPS. This is known as a mixed content error, and it prevents browsers from considering the page fully secure.

Quick Fix Steps

  1. Open your website in Google Chrome or Microsoft Edge.
  2. Right-click anywhere on the page and select Inspect or press F12.
  3. Click the Console tab in the developer tools panel.
  4. Refresh the page and look for warnings containing the phrase "Mixed Content" or "blocked: mixed-content".
  5. Note the full URLs listed in these warnings so you can update them in your website files.

Detailed Instructions

Identify Mixed Content Errors

Modern browsers block insecure content loaded on secure pages to protect visitors. When an image or script is called using http:// instead of https://, the browser will refuse to load it and log an error in the console. These blocked assets often appear as broken images or missing styles on your live site.

Update Hard-Coded Links in Website Code

Warning: Before editing any theme files, child themes, or custom CSS, create a full backup of your website. Hard-coded HTTP links in theme files or custom stylesheets can override global settings and continue to trigger mixed content warnings even after you update your CMS configuration.
  1. Connect to your hosting account using FTP or your hosting control panel's file manager.
  2. Open your theme files, template files, or page source in a text editor.
  3. Search for any instance of http:// within image tags, stylesheet links, or script references.
  4. Change http:// to https:// for assets hosted on your own domain.
  5. Save the file and upload it back to the server if you edited it locally.
  6. Clear your website cache and refresh the page to verify the assets load correctly.

Only change links to assets hosted on your own domain. Linking to external resources over HTTPS may still fail if the third-party server does not support a secure connection.

Update Content Management System Settings

If you use a content management system such as WordPress, Joomla, or Drupal, the site URL may still be configured to use HTTP.

WordPress

  1. Log in to your WordPress administration dashboard.
  2. Navigate to Settings > General.
  3. Update the WordPress Address (URL) and Site Address (URL) fields to use https://.
  4. Click the Save Changes button.
  5. Clear any caching plugins and refresh the page.

Joomla

  1. Log in to your Joomla administrator panel.
  2. Navigate to System > Global Configuration.
  3. Click the Site tab.
  4. Set Force HTTPS to On or Entire Site.
  5. Click Save & Close.

Drupal

  1. Log in to your Drupal administration dashboard.
  2. Navigate to Admin > Configuration > System > Site information.
  3. Update the Site name and site URL fields to use https://.
  4. Click the Save configuration button.

Search and Replace URLs in the Database

Old HTTP links may be stored inside your website database, particularly within post content, page content, and widget areas. A simple find-and-replace across your database can update these references in bulk.

Warning: Always back up your database before running a search and replace operation. Incorrect database changes can break your website.
  1. Create a full backup of your website database.
  2. Use a search and replace tool compatible with your content management system.
  3. Search for your domain using http:// and replace it with https://.
  4. Run the replacement and verify that mixed content warnings no longer appear.

Troubleshooting

Check .htaccess Redirect Rules

Your server configuration may not be redirecting all traffic to HTTPS. Check your .htaccess file for redirect rules.

  1. Connect to your hosting account using FTP or file manager.
  2. Locate the .htaccess file in your website's root directory.
  3. Confirm that a 301 redirect rule is present to force all HTTP traffic to HTTPS.
  4. Ensure the redirect is applied site-wide, not just to the homepage.
  5. Save the file and test your website in a private browsing window.

Check CDN and Cloudflare SSL Settings

If you use a content delivery network such as Cloudflare, incorrect SSL settings can cause mixed content errors.

Content Security Policy Headers

Content Security Policy (CSP) headers can block mixed content even after you update your URLs. If your site sends a CSP header with upgrade-insecure-requests or specific img-src and script-src directives, verify that these policies allow HTTPS resources. Adjust your CSP headers in your server configuration or .htaccess file if assets are still being blocked.

Images Still Not Loading After Updates

External Images or Embedded Content

Resolving mixed content errors ensures that your website displays the full padlock icon, protects visitor data, and maintains trust with your audience. 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