Steve85b

Try it out on your free dummy site: Click here => <a href="https://tastewp.com/plugins/http-https-remover" rel="nofollow ugc">https://tastewp.com/plugins/http-https-remover</a>. 
(this trick works for all plugins in the WP repo – just replace “wordpress” with “tastewp” in the URL)
UPDATE: This plugin will be maintained again! It changed ownership and we’re currently collecting ideas how to further improve it. If you have any cool ideas, please let us know in Support Forum. Thank you!
Major updated in the latest release (3.0): 
– Plugin has a proper settings page now 
– Many bugs fixed 
– Code optimized, causing performance to increase a lot
Main features:
<ul>
<li>Works in Front- and Backend</li>
<li>Makes every Plugin compatible with https</li>
<li>Compatible with WPBakery & Disqus</li>
<li>Fixes Google Fonts issues</li>
<li>Makes your website faster</li>
</ul>
<h4>What does this Plugin do?</h4>
With protocol relative url’s you simply leave off the http: or https: part of the resource path. The browser will automatically load the resource using the same protocol that the page was loaded with.
For example, an absolute url may look like
<pre><code>src="http://domain.com/script.js"
</code></pre>
If you were to load this from a https page the script will not be loaded – as non-https resources are not loaded from https pages (for security reasons).
The protocol relative url would look like
<pre><code>src="//domain.com/script.js"
</code></pre>
and would load if the web page was http or https.
Tipp: Check your Settings -> General page and make sure your WordPress Address and Site Address are starting with “https”. 
Add the following two lines in your wp-config.php above the line that​ says “Stop Editing Here”:
<pre><code>define('FORCE_SSL', true);
define('FORCE_SSL_ADMIN',true);
</code></pre>
<h4>What is Mixed Content?</h4>
Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS. Modern browsers display warnings about this type of content to indicate to the user that this page contains insecure resources.
Note: You should always protect all of your websites with HTTPS, even if they don’t handle sensitive communications.
<h4>Example</h4>
Without Plugin: 
 src=”http://domain.com/script01.js” 
 src=”https://domain.com/script02.js” 
 src=”//domain.com/script03.js”
With Plugin: 
 src=”//domain.com/script01.js” 
 src=”//domain.com/script02.js” 
 src=”//domain.com/script03.js”
<h4>If using Cache Plugins</h4>
If the plugin isn’t working like expected please purge/clear cache for the changes to take effect!

SSL Mixed Content Fix

This is really simple plugin and easy to configure. It works fine and really useful.

Awesome Plugin

A fix for mixed content! This Plugin creates protocol relative urls by removing http + https from links. Works in Front- and Backend!

webaware

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 <a href="https://ssl.webaware.net.au/" rel="nofollow ugc">SSL Insecure Content Fixer website</a> for more details.
<h3>Translations</h3>
Many thanks to the generous efforts of our translators:
<ul>
<li>Bulgarian (bg_BG) — <a href="https://translate.wordpress.org/locale/bg/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Bulgarian translation team</a></li>
<li>Chinese simplified (zh_CN) — <a href="https://translate.wordpress.org/locale/zh-cn/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Chinese translation team</a></li>
<li>English (en_CA) — <a href="https://translate.wordpress.org/locale/en-ca/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the English (Canadian) translation team</a></li>
<li>English (en_GB) — <a href="https://translate.wordpress.org/locale/en-gb/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the English (British) translation team</a></li>
<li>English (en_ZA) — <a href="https://translate.wordpress.org/locale/en-za/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the English (South African) translation team</a></li>
<li>Dutch (nl_NL) — <a href="https://translate.wordpress.org/locale/nl/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Dutch translation team</a></li>
<li>German (de_DE) — <a href="https://translate.wordpress.org/locale/de/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the German translation team</a></li>
<li>French (fr_FR) — <a href="https://translate.wordpress.org/locale/fr/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the French translation team</a></li>
<li>Italian (it_IT) — <a href="https://translate.wordpress.org/locale/it/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Italian translation team</a></li>
<li>Japanese (ja) — <a href="https://translate.wordpress.org/locale/ja/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Japanese translation team</a></li>
<li>Russian (ru_RU) — <a href="https://translate.wordpress.org/locale/ru/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Russian translation team</a></li>
<li>Spanish (es_ES) — <a href="https://translate.wordpress.org/locale/es/default/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">the Spanish translation team</a></li>
</ul>
If you’d like to help out by translating this plugin, please <a href="https://translate.wordpress.org/projects/wp-plugins/ssl-insecure-content-fixer" rel="nofollow ugc">sign up for an account and dig in</a>.
<h3>Privacy</h3>
SSL Insecure Content Fixer does not collect any personally identifying information, and does not set any cookies.

SSL Insecure Content Fixer

This plugin is very helpful in making sure that a WordPress site will load fully in HTTPS.

This Plugin Does EXACTLY as it says - GREAT WORK!

Clean up WordPress website HTTPS insecure content

SSL Mixed Content Fix vs SSL Insecure Content Fixer