SSL Insecure Content Fixer


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.


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.


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


  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. Ative o plugin pelo menu “Plugins” no 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. //; 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.

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.

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.


Works great, solved all my issues

Users like me who were issued for example, with the potential problem that secured padlock doesn't appear on the front but does at the backend, etc, can now be solved with this plugin easily. Plugin scanned all the possible issues and errors and helped me to solve the problem that I would not figure out by myself in no time. Thanks for the plugin author!

I’ll Donate Soon!

Green Lock! Had to apply most off the options but it doesn't seem like it impacts load speed or have any ill effects. Works perfectly. Kudos to the developer. Don't know how I would have done it without this plugin.

Fixed All My Issues

For over a year, in between grad school and work, I dabbled with my website and one of the things that drove me crazy was the mixed media message. I delved into the coding itself, was about to deactivate all plugins, and even was able to narrow it down to what areas was causing it. However, I could never find the error personal, though scrolling through various codes. After much research online, and after several failed attempts at fixing the mixed media content, I gave this a whirl. I had to go about two steps above the simple fix but even then with the second highest level, my website was already starting to display correctly with https:// When I finally found the correct level, which was easy peasy and user friendly, my website finally was able to register the lovely SSL certificate I installed ages ago. It took less than five minutes, downloading, installing, reading, pausing not wanting to get my hopes up then seeing this plugin worked. I definitely recommend it for everyone who is trying to get rid of that annoying message, especially after putting in legwork to fix it yourself.
Leia todas as 187 avaliações

Contribuidores e desenvolvedores

“SSL Insecure Content Fixer” é um software com código aberto. As seguintes pessoas contribuíram para este plugin.


“SSL Insecure Content Fixer” foi traduzido para 14 localidades. Obrigado aos tradutores por suas contribuições.

Traduzir “SSL Insecure Content Fixer” para o seu idioma.

Interessado no desenvolvimento?

Navegue pelo código, dê uma olhada no repositório SVN ou assine o registro de desenvolvimento via RSS.

Registro de alterações

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


Released 2018-12-04

  • fixed: some hard-coded link elements (e.g. stylesheets) when href is the first attribute