How to fix mixed content warnings after installing ssl
Summary
This guide helps you troubleshoot and resolve: How to fix mixed content warnings after installing ssl. Follow the steps below to fix the issue.
Quick Tip: Need immediate assistance? 💻 Open a Ticket
Common Causes
When an SSL certificate is installed on your domain but some images, scripts, or stylesheets continue to load via HTTP instead of HTTPS, browsers may display a "Not Secure" warning or block those assets entirely. This is known as mixed content. It occurs when a website is accessed over a secure connection, but certain elements on the page are still being requested over an insecure connection. This article explains how to identify mixed content and update your site so that every asset is served securely.
Quick Fix Steps
- Visit your website using
https://in your browser. - Open the browser developer tools to identify which resources are loading over HTTP.
- Update your site URLs and resource links from
http://tohttps://. - Clear your website cache and reload the page to verify the warning is gone.
Detailed Instructions
Identify Mixed Content in Your Browser
- Open your website in Google Chrome, Microsoft Edge, or Mozilla Firefox using
https://yourdomain.com.au. - Right-click anywhere on the page and select Inspect, or press
F12to open developer tools. - Click the Console tab. Look for warnings that say "Mixed Content" or "Blocked mixed content." These messages list the exact URLs being loaded insecurely.
- Alternatively, click the Network tab, refresh the page, and look for any requests starting with
http://instead ofhttps://.
Update Your Site Address and Resource Links
- Log in to your website's admin dashboard or content management system.
- Navigate to the general settings or site URL configuration.
- Change the site address and home URL from
http://tohttps://, then save your changes. - If you use WordPress, go to Settings > General. Update both the WordPress Address (URL) and Site Address (URL) fields to start with
https://, then click Save Changes. - If you use cPanel, log in to your hosting account and look for the Domains or SSL/TLS section to ensure your primary domain is configured for HTTPS.
- If you use Plesk, navigate to Websites & Domains, select your domain, and check the SSL/TLS Certificates settings to enable HTTPS.
- For hard-coded links in your theme or template files, update any
http://references tohttps://, or use protocol-relative URLs such as//yourdomain.com.au/image.jpg.
Update Internal Links and Hardcoded URLs in Content
- After changing your site URL in the admin settings, update any remaining internal links within your page and post content that still point to
http://. - For WordPress, install a reputable search and replace plugin such as Better Search Replace or Velvet Blues Update URLs.
- Run a search for your old domain using
http://yourdomain.com.auand replace it withhttps://yourdomain.com.au. - Pay close attention to the database tables that store post content, widget settings, and theme options.
- After the replacement is complete, deactivate and remove the plugin to keep your site lean.
Always create a full backup of your website files and database before running a search and replace operation or editing theme files. Incorrect replacements can break your site layout or prevent it from loading.
Update Hardcoded URLs in Theme Files via FTP or File Manager
- Access your website files via FTP or your hosting control panel's file manager.
- Navigate to your active theme directory, typically found in
/wp-content/themes/your-theme-name/for WordPress. - Open template files such as
header.php,footer.php, andfunctions.phpin a text editor. - Search for any instances of
http://and replace them withhttps://or protocol-relative URLs. - Save the files and upload them back to the server if you are using FTP.
Force HTTPS with a Redirect
- Access your website files via FTP or your hosting control panel's file manager.
- Locate the
.htaccessfile in your root directory for Apache servers. If your server uses Nginx, contact support for the correct redirect rule. - Add a redirect rule that sends all HTTP traffic to HTTPS, ensuring visitors and search engines always use the secure version of your site.
- Save the file and test your website by visiting
http://yourdomain.com.auto confirm it automatically redirects to HTTPS.
Always back up your
.htaccess file before making changes. Test your redirects thoroughly after saving to ensure no redirect loops occur and that all pages load securely.Implement HSTS (HTTP Strict Transport Security)
- HSTS tells browsers to always connect to your site using HTTPS, even if a user types
http://. - Add the HSTS header to your
.htaccessfile or server configuration. - Only enable HSTS after you have confirmed that your entire site works correctly over HTTPS and that your SSL certificate is valid.
- Test your site thoroughly after enabling HSTS, as it can prevent access if your certificate expires or is misconfigured.
Troubleshooting
Warning Persists After Updating URLs
- Clear your website cache, including any caching plugin, server-side cache, or CDN cache.
- Clear your browser cache or test in an incognito/private window.
- Check that external resources, such as embedded videos, fonts, or analytics scripts, support HTTPS. If an external resource only works over HTTP, contact the provider or host the asset locally.
- Check third-party themes and plugins for hardcoded HTTP URLs. Update them via the plugin settings, theme customiser, or by editing the theme files directly.
- Check cron jobs and email configurations that may reference HTTP URLs and update them to HTTPS.
- Check email templates and newsletter links to ensure they point to secure pages on your website.
Cloudflare Flexible SSL Mixed Content Issues
- If you use Cloudflare, check your SSL/TLS encryption mode in the Cloudflare dashboard.
- Avoid using Flexible SSL mode, as it can cause redirect loops and mixed content warnings.
- Change the setting to Full or Full (Strict) to ensure traffic between Cloudflare and your origin server is encrypted.
- Purge your Cloudflare cache after changing SSL settings.
Green Padlock Still Not Showing
- Ensure every single asset on the page—including images, CSS, JavaScript, and iframes—is loaded over HTTPS.
- Use an online mixed content checker to scan your page for remaining insecure resources.
- Confirm your SSL certificate is installed correctly and covers both the root domain and the www subdomain if needed.
Update Search Console and Analytics After Migration
- Add the HTTPS version of your website as a new property in Google Search Console.
- Submit your updated sitemap to help Google index your secure pages.
- Update your Google Analytics property settings to use the HTTPS URL.
- Monitor Search Console for any coverage or indexing issues after the migration.
Incorrect redirects or missing canonical tags during an HTTPS migration can impact your SEO rankings. Ensure all HTTP URLs redirect to their HTTPS equivalents and verify your settings in Google Search Console.
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
💻 Open a Ticket