SSL Insecure Content Fixer

Description

Clean up your WordPress website’s HTTPS insecure content and mixed content warnings. Installing the SSL Insecure Content Fixer plugin will solve most insecure content warnings with little or no effort. The remainder can be diagnosed with a few simple tools.

When you install SSL Insecure Content Fixer, its default settings are activated and it will automatically perform some basic fixes on your website using the Simple fix level. You can select more comprehensive fix levels as needed by your website.

WordPress Multisite gets a network settings page. This can be used to set default settings for all sites within a network, so that network administrators only need to specify settings on sites that have requirements differing from the network defaults.

See the SSL Insecure Content Fixer website for more details.

Translations

Many thanks to the generous efforts of our translators:

If you’d like to help out by translating this plugin, please sign up for an account and dig in.

Privacy

SSL Insecure Content Fixer does not collect any personally identifying information, and does not set any cookies.

Contributions

Installation

  1. Either install automatically through the WordPress admin, or download the .zip file, unzip to a folder, and upload the folder to your /wp-content/plugins/ directory. Read Installing Plugins in the WordPress Codex for details.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.

If your browser still reports insecure/mixed content, have a read of the Cleaning Up page.

FAQ

Installation Instructions
  1. Either install automatically through the WordPress admin, or download the .zip file, unzip to a folder, and upload the folder to your /wp-content/plugins/ directory. Read Installing Plugins in the WordPress Codex for details.
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.

If your browser still reports insecure/mixed content, have a read of the Cleaning Up page.

How do I tell what is causing the insecure content / mixed content warnings?

Look in your web browser’s error console.

NB: after you open your browser’s console, refresh your page so that it tries to load the insecure content again and logs warnings to the error console.

Why No Padlock? has a really good online test tool for diagnosing HTTPS problems.

I get “insecure content” warnings from some of my content

You are probably loading content (such as images) with a URL that starts with “http:”. Take that bit away, but leave the slashes, e.g. //www.example.com/image.png; your browser will load the content, using HTTPS when your page uses it. Better still, replace “http:” with “https:” so that it always uses https to load images, e.g. https://www.example.com/image.png.

If your page can be used outside a web browser, e.g. in emails or other non-web documents, then you should always use a protocol and it should probably be “https:” (since you have an SSL certificate). See Cleaning up content for more details.

My website is behind a load balancer or reverse proxy

If your website is behind a load balancer or other reverse proxy, and WordPress doesn’t know when HTTPS is being used, you will need to select the appropriate HTTPS detection settings. See my blog post, WordPress is_ssl() doesn’t work behind some load balancers, for some details.

I get warnings about basic WordPress scripts like jquery.js

You are probably behind a reverse proxy — see the FAQ above about load balancers / reverse proxies, and run the SSL Tests from the WordPress admin Tools menu.

I changed the HTTPS Detection settings and now I can’t login

You probably have a conflict with another plugin that is also trying to fix HTTPS detection. Add this line to your wp-config.php file, above the lines about ABSPATH. You can then change this plugin back to default settings before proceeding.

define('SSLFIX_PLUGIN_NO_HTTPS_DETECT', true);
I still get “insecure content” warnings on my secure page

Post about it to the support forum, and be sure to include a link to the page. Posts without working links will probably be ignored.

You listed my plugin, but I’ve fixed it

Great! Tell me which plugin is yours and how to check for your new version, and I’ll drop the “fix” from my next release.

Reviews

fast and easy

installed, activated, a couple of clicks in settings and done. thanks

THANK YOU!

I have been having an error on my website, redirecting error and nothing I could do would fix it.

I finally narrowed it down to that it worked without SSL, but not with. But didn’t know why, I used your tool and it tells me I am behind a reverse proxy, none of the other domains on this server do that, so you helped SO MUCH.

Thank you!!

This

just saved me hours of headaches. You can use it even with older themes that totally break when you do anything manually in the database. THANK. YOU!

Fantastic

I just used Really Simple SSL, but it kept failing to show a green padlock.
Really Simple SSL offer to fix the issues for $26.00.
This plug in did it for free.

If it still works in a few days then I will definitely be donating to the author.

Read all 165 reviews

Contributors & Developers

“SSL Insecure Content Fixer” is open source software. The following people have contributed to this plugin.

Contributors

“SSL Insecure Content Fixer” has been translated into 13 locales. Thank you to the translators for their contributions.

Translate “SSL Insecure Content Fixer” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

The full changelog can be found on GitHub. Recent entries:

2.7.0, 2018-06-30

  • added: fix for responsive images loaded by JavaScript from image data attributes
  • fixed: call to undefined function hash_equals() on environments with obsolete PHP versions (i.e. < 5.6)
  • fixed: don’t run the fixer when a WooCommerce download request is detected