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.
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
- Open your website in Google Chrome, Microsoft Edge, or Mozilla Firefox.
- Press
F12to open Developer Tools and select the Console tab. - Refresh the page and look for warnings containing
Mixed ContentorBlocked. - Note the insecure URLs listed (they will begin with
http://). - Update those URLs in your website code or content management system to use
https://. - Clear your browser cache and refresh the page to confirm the warnings are gone.
Detailed Instructions
Identify Mixed Content Errors
- Visit your website using
https://in your browser. - Look for the padlock icon in the address bar. If it shows a warning triangle or says "Not secure," mixed content is likely present.
- Right-click anywhere on the page and select Inspect or press
F12. - Click the Console tab in Developer Tools.
- Refresh the page using
F5orCtrl + R(Windows) /Cmd + R(Mac). - 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
- Open your website files using an FTP client, file manager, or your content management system.
- Search your HTML, CSS, JavaScript, and template files for instances of
http://. - Change internal resource links from
http://tohttps://. 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">
- If you use a CMS such as WordPress, update the WordPress Address (URL) and Site Address (URL) under Settings > General to use
https://. - Save your changes and upload the modified files if necessary.
Force HTTPS Redirects
- Access your website's
.htaccessfile via FTP or file manager (Apache servers). - Add a redirect rule to send all HTTP traffic to HTTPS.
- Save the file and test your website by visiting
http://yourdomain.com.au— it should automatically redirect tohttps://yourdomain.com.au. - 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
- Clear your browser cache. In Chrome or Edge, press
Ctrl + Shift + Delete(Windows) orCmd + Shift + Delete(Mac), select cached images and files, and clear them. - Clear any caching plugins or server-side caching active on your website.
- Check hard-coded links in theme files, widgets, or embedded content that may still reference
http://.
Third-Party Resources Load Over HTTP
- If images, fonts, or scripts are hosted on an external domain, confirm that domain supports HTTPS.
- Update the resource URL to
https://or host the asset locally on your own secure server. - Avoid loading resources from domains that do not offer a secure version.
SSL Certificate Issues
- Ensure your SSL certificate is valid and not expired. An expired certificate will trigger security warnings even if mixed content is resolved.
- Confirm the certificate covers both the root domain (
yourdomain.com.au) and thewwwsubdomain if applicable.
.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.
Still Having Issues?
💻 Open a Ticket