Jaidev Bangar

After moving a site to HTTPS, many WordPress databases still contain <code>http://</code> references to your own domain in posts, meta, and options. That can cause mixed content warnings and broken images in the browser.
Solaxes HTTPS Migration Repair helps administrators:
<ul>
<li>Scan selected WordPress database tables for HTTP URLs on your own domain only</li>
<li>Target content types: images, pages, posts, CSS, JavaScript, and other references</li>
<li>Live preview (frontend only): rewrite HTTP to HTTPS in page output without database changes</li>
<li>Review summarized scan results by content type</li>
<li>Export detailed findings as CSV or JSON</li>
<li>Run a dry run before applying changes</li>
<li>Apply serialized-safe HTTP to HTTPS repairs in batches</li>
</ul>
This plugin helps detect and repair common HTTP references stored in the database. It does not guarantee that every mixed content issue on a site will be resolved. It does not rewrite third-party <code>http://</code> links, and it does not modify theme or plugin files on disk. Always take a full database backup before applying permanent changes.
Developed by <a href="https://solaxes.com/" rel="nofollow ugc">Solaxes Technologies</a>.
<h3>Privacy Policy</h3>
This plugin processes data only on your WordPress site:
<ul>
<li>Database scan and repair — Reads and optionally updates your site database on your server. No scan results are sent off-site automatically.</li>
<li>Live preview — Rewrites frontend HTML output on your server. The database is not changed while live preview is enabled.</li>
<li>Support & Feedback form (optional) — If you submit the in-app form, an email is sent via your site’s <code>wp_mail()</code> to Solaxes Technologies. The message may include your WordPress account email (Reply-To), site URL, WordPress version, and plugin version. You choose whether to include extra technical context. No automatic telemetry is collected.</li>
</ul>
Administrators can change the support recipient with the <code>solaxes_hmr_support_email</code> filter.

Solaxes HTTPS Migration Repair

Scan your WordPress database for common HTTP mixed content URLs on your own domain and repair them safely after SSL migration.

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!

Solaxes HTTPS Migration Repair vs SSL Mixed Content Fix