{"id":4432,"date":"2026-10-26T07:50:12","date_gmt":"2026-10-26T07:50:12","guid":{"rendered":"https:\/\/www.wpchatsupport.com\/blog\/?p=4432"},"modified":"2026-10-26T08:07:24","modified_gmt":"2026-10-26T08:07:24","slug":"fix-wordpress-mixed-content-error-after-ssl","status":"publish","type":"post","link":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/","title":{"rendered":"How to Fix WordPress Mixed Content Error After SSL"},"content":{"rendered":"<h2>Introduction<\/h2>\n<p>You installed your SSL certificate. You switched the site to https. You expected a padlock. Instead your browser says &#8220;Not secure&#8221;, and parts of your site have stopped working.<\/p>\n<p>Maybe your images vanished. Maybe your layout fell apart because a stylesheet never loaded. Maybe a map or a video embed is now a blank box. Maybe your contact form warns people before they can send it.<\/p>\n<p>This is the WordPress mixed content error. The page itself arrived securely. But something inside the page still asks for a file over plain http. Your browser spots that gap and acts on it.<\/p>\n<p>The cost is real. Visitors see a security warning on a page you just made secure. Trust drops immediately. Forms stop filling in automatically, and some visitors will not submit them at all. Broken layouts cost you sales on the pages that matter most.<\/p>\n<p>This guide covers the whole problem. You will learn exactly what your browser does and why. You will learn how to find the one insecure file causing it. Then you will fix every cause, in order, from the safest change to the deepest.<\/p>\n<p>The usual triggers are easy to recognise. A site move. A fresh certificate on an older site. A page builder holding old links. A caching layer serving yesterday&#8217;s page. A Cloudflare setting that hides the secure connection from WordPress. Every one of these has a known fix.<\/p>\n<h2>Signs That Show a WordPress Mixed Content Error<\/h2>\n<p>Confirm you have this problem before you change anything. Several SSL faults look similar from the outside, and they need different fixes.<\/p>\n<p>The clearest sign sits in your address bar. You loaded the page over https, yet the browser shows &#8220;Not secure&#8221; rather than a padlock. Click that label. Chrome will tell you the page is not secure and offer to show you the details.<\/p>\n<p>The second sign is visible damage that only started after the SSL switch. Look for these patterns:<\/p>\n<ul>\n<li><strong>Images missing on some pages but fine on others.<\/strong> The broken ones were added before the switch.<\/li>\n<li><strong>Layout collapsed or unstyled.<\/strong> A stylesheet was blocked, so the page shows raw HTML.<\/li>\n<li><strong>Buttons, sliders, or menus doing nothing.<\/strong> A script was blocked, so the behaviour never loaded.<\/li>\n<li><strong>Maps, videos, or embeds showing as blank boxes.<\/strong> Frames are blocked outright.<\/li>\n<li><strong>Fonts falling back to a plain system font.<\/strong> Web fonts are blocked too.<\/li>\n<li><strong>A warning when someone fills in your form.<\/strong> The form sends to an insecure address.<\/li>\n<\/ul>\n<p>The third sign is the one that proves it. Open your browser&#8217;s developer tools and look at the Console. You will see messages that start with the words Mixed Content. There are two kinds, and the difference matters.<\/p>\n<p>A blocked item reads like this: the page was loaded over HTTPS, but requested an insecure resource, and the request has been blocked. That is a red error. The file never loaded at all.<\/p>\n<p>An upgraded item reads differently: the request was automatically upgraded to HTTPS. That is a yellow warning. The browser fixed it for you this time. It still means an http link is sitting in your page, waiting to break the day that file has no secure version.<\/p>\n<p>Now rule out the lookalikes:<\/p>\n<ul>\n<li><strong>Your browser warns that the connection is not private.<\/strong> That is a certificate problem, not mixed content. The whole page fails, not parts of it.<\/li>\n<li><strong>The site bounces endlessly and shows a redirect error.<\/strong> Read our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-err-too-many-redirects-wordpress\/\">ERR_TOO_MANY_REDIRECTS in WordPress<\/a>.<\/li>\n<li><strong>Images are broken but the padlock is fine.<\/strong> That is a separate issue. See our fix for <a href=\"https:\/\/www.wpchatsupport.com\/blog\/broken-images-in-wordpress\/\">broken images in WordPress<\/a> and for <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-fix-wordpress-media-library-images-not-showing\/\">media library images not showing<\/a>.<\/li>\n<li><strong>The dashboard sends you to your homepage.<\/strong> See our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-admin-redirecting-to-homepage\/\">WordPress admin redirecting to the homepage<\/a>.<\/li>\n<\/ul>\n<p>One more thing to know before you start. Console messages only cover the page you are looking at. The console clears when you move to a new page. So a clean homepage does not mean a clean site. You have to check your important pages one by one, or use a crawler that does it for you.<\/p>\n<h2>Reasons Why the WordPress Mixed Content Error Happens<\/h2>\n<p>Before the causes, here is what your browser actually does. Knowing this makes every fix below make sense.<\/p>\n<p>Browsers now split insecure items into two groups. Images, audio, and video loaded through a plain source attribute get upgraded automatically. The browser tries them over https instead. If that works, the file loads and you get a warning. If it fails, the file does not load at all.<\/p>\n<p>Everything else is simply blocked. That means scripts, stylesheets, frames, web fonts, and background requests. It also covers every file referenced inside your CSS, and images loaded through a responsive image set. There is no warning and no fallback for these. They are refused.<\/p>\n<p>That split explains most of what you are seeing. Now here are the ten causes behind it.<\/p>\n<h3>Your two site addresses still start with http<\/h3>\n<p>WordPress stores two addresses. The Site Address is what visitors type. The WordPress Address is where the core files live. They are saved in your database as <code>home<\/code> and <code>siteurl<\/code>.<\/p>\n<p>Nearly every link WordPress builds starts from those values. If either one still begins with http, WordPress will keep writing http into your pages. Your media URLs, your theme files, your plugin files, and your responsive image sets all inherit it. This is the single most common cause.<\/p>\n<h3>WordPress cannot tell that the page is secure<\/h3>\n<p>WordPress works out whether a request is secure by reading only two server values. It checks whether an HTTPS flag is set, and whether the port is 443. It reads no forwarded headers at all.<\/p>\n<p>That matters when your certificate lives somewhere other than your own server. A load balancer, a reverse proxy, or Cloudflare can handle the certificate for you. It then talks to your server over plain http. Your server sees an insecure request. WordPress agrees with it. So WordPress writes http links into a page that the visitor loaded over https.<\/p>\n<p>Your stored addresses can say https and this still happens. The scheme in your links comes from this live check, not only from the stored value.<\/p>\n<h3>Old http links saved inside your posts and pages<\/h3>\n<p>WordPress saves content, not just templates. Every image you inserted was stored with the address you had at the time. Every link you pasted was too. Those addresses do not update themselves when you switch to https.<\/p>\n<p>So a post written three years ago still points at the http version of its own images. The post content lives in your posts table as plain HTML. It is the easiest place to fix and the easiest to find.<\/p>\n<h3>http URLs buried inside packed settings<\/h3>\n<p>This is the cause that catches people out. WordPress stores a lot of settings as packed data, not plain text. Widget options, theme settings, custom fields, and plugin options all use this format.<\/p>\n<p>The format records the length of every piece of text. That length sits just before the text itself. So you cannot simply run a find and replace query on your database. The words http and https are different lengths. Replace one with the other and the recorded length no longer matches the real text. The setting then fails to unpack at all.<\/p>\n<p>The result is worse than the original problem. Widgets disappear. Theme settings reset. Builder layouts go blank. WordPress documents this risk itself. It warns that a whole-database replace can break things for exactly this reason.<\/p>\n<h3>Page builder data and the CSS files it writes<\/h3>\n<p>Page builders add a second layer to the same problem. Elementor, for example, saves each layout as structured data in a hidden custom field. It also writes CSS files to disk. Background images inside those files are saved as full addresses.<\/p>\n<p>So a normal database replace can miss them twice. It may not reach the builder&#8217;s stored data correctly, and it certainly does not touch files on disk. Elementor&#8217;s own documentation says this plainly, which is why it ships its own replace tool.<\/p>\n<h3>Theme or plugin code with http written into it<\/h3>\n<p>Some insecure links are not in your database at all. They are in code. A theme or plugin that loads a script using a full http address will keep doing it forever. No database tool can reach it.<\/p>\n<p>The same goes for a CSS file in your theme that references an image over http. The fix has to happen in the file itself, or in the correct WordPress function that builds the address for you.<\/p>\n<h3>Third-party resources with no secure version<\/h3>\n<p>Sometimes nothing on your site is wrong. The remote service simply has no https address. An old analytics script, a legacy font host, a widget from a small supplier, or an image hosted on an ancient server.<\/p>\n<p>Under current browser rules there is no way around this. A blocked item cannot be allowed by anything you write in your page. Only the visitor can override it in their own settings, and you cannot ship that choice to them.<\/p>\n<h3>Caching serving the old version of your page<\/h3>\n<p>Every cache stores a finished page, not the database rows behind it. So you can fix your database completely and still be served yesterday&#8217;s HTML.<\/p>\n<p>There are usually several layers. Your caching plugin. Your host&#8217;s own page cache. An object cache holding query results. A reverse proxy. A CDN edge. And finally the visitor&#8217;s own browser. Any one of them can keep the old http links alive.<\/p>\n<p>The order you clear them in matters, and Cloudflare explains why. If you purge the edge while your own server still builds the old page, the very next request pulls the old page straight back in.<\/p>\n<h3>Cloudflare settings that do less than people expect<\/h3>\n<p>Cloudflare has two features people reach for here, and both have limits worth knowing.<\/p>\n<p>Always Use HTTPS redirects the visitor&#8217;s page request from http to https. It does not touch the contents of the page. Cloudflare says so directly: forcing HTTPS does not resolve mixed content, because browsers check each resource before requesting it.<\/p>\n<p>Automatic HTTPS Rewrites does rewrite links inside the page. But it only rewrites a link once it has confirmed the file is reachable over https. And Cloudflare&#8217;s own documentation adds an important limit. If your domain is not on the lists it consults, only active content gets rewritten. Passive content such as images is left alone and still causes mixed content errors.<\/p>\n<p>Flexible mode is the bigger trap. It gives visitors https while talking to your server over plain http, which triggers the detection problem described above.<\/p>\n<h3>The HTTP to HTTPS redirect is missing or misplaced<\/h3>\n<p>This one is worth stating clearly, because it is the most common follow-up question. People add the redirect, see the padlock still broken, and assume the redirect failed.<\/p>\n<p>It did not. A redirect only handles the page request itself. The browser follows it, loads the secure page, reads the HTML, and then makes fresh requests for every file listed inside. Those requests are judged before any redirect could apply to them. So the redirect is necessary, but it will never fix mixed content on its own.<\/p>\n<h2>How to Fix the WordPress Mixed Content Error (Step by Step)<\/h2>\n<p>Work through these in order. Each one tells you how to confirm it applies to you first, so you never change settings blindly.<\/p>\n<p>Start by finding the exact insecure file. It takes a minute and saves hours. Open the page in Chrome and press the key combination for developer tools. Open the Console tab and read the Mixed Content messages. Each one names the page and the exact file address causing it. You can also type <code>mixed-content:all<\/code> into the filter box on the Network tab to list every offending request at once.<\/p>\n<p>Write down what you find. If the address is in your own uploads folder, you have a database problem, so look at Steps 3 to 5. If it is in your theme or plugin folder, go to Step 6. If it is on someone else&#8217;s domain, go to Step 7.<\/p>\n<p><strong>Take a full backup before you begin.<\/strong> Several steps write to your database or edit your config file. Both can take a live site down. Back up your files and database, or do the work on a staging copy and push it live afterwards. Our guide to <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-backup-wordpress-using-updraftplus\/\">backing up WordPress with UpdraftPlus<\/a> walks through it.<\/p>\n<h3>Step 1: Update your Site Address and WordPress Address to https<\/h3>\n<p>This step addresses the http site addresses cause. Those two values seed almost every link WordPress writes, so leaving either on http keeps the problem alive no matter what else you fix.<\/p>\n<p>Confirm it first. Open your dashboard, go to Settings, and open the General screen. Read the WordPress Address and the Site Address fields. A healthy site shows https at the start of both, with no slash on the end. A broken site shows http on one or both.<\/p>\n<p>If the two fields will not let you type in them, stop. That means the values are being set by constants in your config file instead. Open wp-config.php and look for <code>WP_HOME<\/code> and <code>WP_SITEURL<\/code>. Fix them there, because editing the database will not help while those lines exist.<\/p>\n<p>To fix it from the dashboard, change both fields to the https version and save. WordPress will log you out, which is normal. Log back in over https.<\/p>\n<p>If you cannot reach the dashboard, use the command line instead:<\/p>\n<pre><code>wp option update home 'https:\/\/example.com'\r\nwp option update siteurl 'https:\/\/example.com'<\/code><\/pre>\n<p>WordPress publishes these exact commands, along with the rule that both values should include the https part and should not end with a slash.<\/p>\n<p>Multisite networks are different. Sub-site addresses are edited in the Network Admin area under Sites, not in the per-site Settings screen.<\/p>\n<p>To verify, load a front-end page and view its source. Search the source for your domain preceded by http. Your theme and plugin files should now all be https. Content images may still be http, which Step 3 handles.<\/p>\n<h3>Step 2: Tell WordPress it sits behind a secure proxy<\/h3>\n<p>This step addresses the detection cause. Do it before any database work, because otherwise WordPress will keep writing http links over the top of everything you fix.<\/p>\n<p>Confirm it carefully. Ask your host whether your certificate terminates at a load balancer, a proxy, or Cloudflare. Then have them report three things. Is the HTTPS server value set? What is the server port? And what does the forwarded protocol header contain? A small test script can report all three.<\/p>\n<p>A healthy direct setup shows the HTTPS value set to on, with port 443. A proxy setup that needs this fix shows the HTTPS value missing, the port as 80, and the forwarded header saying https. That exact combination is your proof. A second clue is a redirect loop appearing the moment you force https anywhere.<\/p>\n<p>The fix is a short snippet that WordPress itself publishes for reverse proxy setups. Add it to wp-config.php, above the line that loads wp-settings.php:<\/p>\n<pre><code>define( 'FORCE_SSL_ADMIN', true );\r\nif ( strpos( $_SERVER['HTTP_X_FORWARDED_PROTO'], 'https' ) !== false )\r\n    $_SERVER['HTTPS'] = 'on';<\/code><\/pre>\n<p>The test looks for https inside the header rather than matching it exactly. That is deliberate. Some setups send a list of values, so an exact match fails.<\/p>\n<p>There is a real security point attached to this. Apache&#8217;s own documentation puts it bluntly. Only trust that forwarded header if you control the proxy in front of your server and it rewrites the header on every request. Otherwise someone connecting to your server directly could send it themselves.<\/p>\n<p>Editing wp-config.php can take a site offline with a single typo. Copy the file before you touch it, and use a plain text editor.<\/p>\n<p>To verify, reload a front-end page and view the source. Theme and plugin links should now start with https. If you have Cloudflare, also complete Step 9, because changing the mode there is the cleaner long-term answer.<\/p>\n<h3>Step 3: Replace the old http links inside your posts and pages<\/h3>\n<p>This step addresses the links saved in content. These are the images and links stored in your posts table. It is the safest database change you can make, because post content is plain HTML with no packed data in it.<\/p>\n<p>Confirm it first, and do it without writing anything. If you have command line access, run a dry run:<\/p>\n<pre><code>wp search-replace 'http:\/\/example.com' 'https:\/\/example.com' --dry-run --skip-columns=guid --report-changed-only<\/code><\/pre>\n<p>That reports how many fields would change and saves nothing. If the count is zero, this is not your cause. You can also check by hand in phpMyAdmin, by counting rows in your posts table whose content contains your http address.<\/p>\n<p>To fix it, drop the dry run flag and run the same command:<\/p>\n<pre><code>wp search-replace 'http:\/\/example.com' 'https:\/\/example.com' --skip-columns=guid --report-changed-only<\/code><\/pre>\n<p>Note the skip-columns part. That protects the GUID column, and WordPress is absolutely firm about it. Never change the contents of the GUID column under any circumstances. It identifies each post to feed readers, and changing it makes every old post look brand new to them.<\/p>\n<p>If you have no command line access, use the Better Search Replace plugin instead. It installs a page under the Tools menu. Select your posts table, enter both addresses, and run it with the dry run option switched on first. The dry run is included in the free version.<\/p>\n<p>Back up your database before any real run. The plugin&#8217;s own documentation says the same, because a wrong search string can damage your data.<\/p>\n<p>To verify, re-run the dry run. It should report zero changes. Then open a few older posts on the front end and confirm their images load.<\/p>\n<h3>Step 4: Run a safe replace for the packed settings<\/h3>\n<p>This step addresses the http URLs buried in packed settings. Your widget options, theme settings, custom fields, and plugin options all live in this format, and a plain SQL replace will destroy them.<\/p>\n<p>Confirm where the problem is before you widen your replace. Run the dry run across more tables:<\/p>\n<pre><code>wp search-replace 'http:\/\/example.com' 'https:\/\/example.com' --dry-run --all-tables-with-prefix --skip-columns=guid --report-changed-only<\/code><\/pre>\n<p>Compare that count with the count from Step 3. A much higher number means you do have http addresses outside your posts table. The command reports which tables they sit in, which tells you what you are dealing with.<\/p>\n<p>Use the right tool and this is straightforward. WordPress has a serialization-aware replace. Its documentation states that the command intelligently handles PHP serialized data and does not change primary key values. It automatically switches from fast queries to careful processing for columns holding packed data.<\/p>\n<p>Run it for real once the dry run looks sensible:<\/p>\n<pre><code>wp search-replace 'http:\/\/example.com' 'https:\/\/example.com' --all-tables-with-prefix --skip-columns=guid --report-changed-only<\/code><\/pre>\n<p>On a multisite network, use the network flag instead so every site&#8217;s tables are covered.<\/p>\n<p>Without command line access, the Better Search Replace plugin handles the same job. Its free version lists serialization support for all tables as a feature. Select all your tables, run the dry run, read the report, then run it properly.<\/p>\n<p>Here is what to avoid. Do not run a plain replace query in phpMyAdmin across your options or postmeta tables. The packed format records the byte length of every string. The word http is seven characters and https is eight. A plain replace makes every string one character longer than its recorded length, and the setting then fails to unpack at all.<\/p>\n<p>Back up your database before this step without exception. This is the riskiest step in the guide. If you can, restore the backup onto a staging copy and run it there first.<\/p>\n<p>To verify, re-run the dry run and expect zero changes. Then check your widgets, your theme options, and a page built with your builder. If anything looks blank, restore your backup rather than trying to repair it by hand.<\/p>\n<h3>Step 5: Replace the URLs in your page builder and clear its files<\/h3>\n<p>This step addresses the page builder cause. Builders store layouts as structured data and also write CSS files to disk. A database replace does not reach those files, so background images keep pointing at http.<\/p>\n<p>Confirm it from what the console told you. Look at where the insecure address points. A file inside a builder&#8217;s own folder is a strong sign. So is a background image that appears nowhere in your post content. Another clue is a page that looks correct inside the builder&#8217;s editor but broken on the live site.<\/p>\n<p>For Elementor, the fix is built in and documented. In your dashboard, go to Elementor, then Editor, and click Tools. Open the Replace URL tab. Enter your old http address and your new https address, then press the Replace URL button. Next, open the General tab and click Clear Files and Data, then save. That erases the generated CSS so it rebuilds with the correct addresses.<\/p>\n<p>If you prefer the command line, Elementor ships its own commands:<\/p>\n<pre><code>wp elementor replace-urls http:\/\/example.com https:\/\/example.com\r\nwp elementor flush-css<\/code><\/pre>\n<p>Elementor also suggests a setting that avoids the file problem entirely. In its editor settings, under performance, you can set the CSS print method to internal embedding rather than external files. Background images then travel with the page instead of living in a separate file.<\/p>\n<p>Other builders are less straightforward. There is no official URL replacement tool documented for WPBakery or Divi. For those, the serialization-aware replace in Step 4 is your main tool, and you should check their output folders for generated CSS afterwards.<\/p>\n<p>Back up before running any builder replace. These tools rewrite your layout data, and the change is not easy to reverse by hand.<\/p>\n<p>To verify, hard-reload a page built with your builder and watch the console. Background images and builder stylesheets should now load over https with no messages.<\/p>\n<h3>Step 6: Find http URLs written into your theme and plugin files<\/h3>\n<p>This step addresses the hard-coded code cause. These links live in PHP, CSS, or JavaScript files, so no database tool will ever touch them.<\/p>\n<p>Confirm it from the file path in your console message. If the insecure address sits inside your theme folder or a plugin folder, and no database replace has changed it, the address is written into the code. You can prove it by searching the files:<\/p>\n<pre><code>grep -rn \"http:\/\/\" wp-content\/themes\/your-theme\/ wp-content\/plugins\/<\/code><\/pre>\n<p>Read the results carefully. An http address inside a link tag or a script tag is a real problem. An http address inside a plain text link that a visitor clicks is usually not mixed content at all, so do not change those by reflex.<\/p>\n<p>To fix your own theme or child theme, replace the hard-coded address with the correct WordPress function. The Plugin Handbook is clear on this. Always use these functions rather than hard-coding paths, because people can move and rename the content directory.<\/p>\n<p>Use <code>get_stylesheet_directory_uri()<\/code> for files in your active theme, and <code>get_template_directory_uri()<\/code> for files in a parent theme. Both check for a secure connection and return the right scheme. Use <code>plugins_url()<\/code> inside a plugin. Use <code>home_url()<\/code> or <code>site_url()<\/code> for general site addresses. Then load your files through the proper enqueue functions rather than printing tags by hand.<\/p>\n<p>For a third-party theme or plugin you did not write, do not edit it directly. Your change will vanish at the next update. Report it to the developer instead. In the meantime, Step 9 or a temporary content fixer plugin can cover you.<\/p>\n<p>If you must edit theme files, use a child theme and work on a staging copy first. A syntax error in a PHP file takes the whole site down.<\/p>\n<p>To verify, hard-reload the page with the cache disabled in developer tools. The console should be clean, and the filter <code>mixed-content:all<\/code> on the Network tab should return nothing.<\/p>\n<h3>Step 7: Fix or remove third-party resources with no secure version<\/h3>\n<p>This step addresses the third-party cause. The console message names a domain that is not yours, and nothing in your own site is at fault.<\/p>\n<p>Confirm whether a secure version exists, using a test the web.dev team recommends. Copy the insecure address into your browser bar. Change the http to https and load it. If it loads, the service does support https and you simply need to update the link. If it fails, the service genuinely has no secure endpoint.<\/p>\n<p>If https works, update the link wherever it lives. That might be in a post, a widget, a theme setting, or a tracking code field. Then re-check the page.<\/p>\n<p>If https does not work, you have only three real options, and web.dev lists them plainly. Load the resource from a different host that does offer https. Download the file and host it on your own site, if you are allowed to. Or remove it from your site altogether.<\/p>\n<p>There is no fourth option. Current browsers block this class of content with no way for you to allow it. A visitor can override it in their own browser settings, but you cannot make that choice on their behalf.<\/p>\n<p>The good news is that the big services are all fine. Google Fonts, the Google Maps embed, the Google tag, YouTube, and Vimeo all publish https embed code today. If you have an http version of any of these, it came from an old tutorial or an old copy of your page. Just swap the scheme.<\/p>\n<p>One warning about old habits. Do not reach for protocol-relative addresses that start with two slashes. They only inherit whatever scheme the page used. They do nothing at all when the remote service has no secure version.<\/p>\n<p>To verify, reload the page and confirm the message for that domain is gone. Then check the feature still works, because removing a blocked script fixes the warning but may remove the function too.<\/p>\n<h3>Step 8: Clear every cache, in the right order<\/h3>\n<p>This step addresses the caching cause. It is also the reason so many people think a correct fix did not work. Your database is clean, but something is still handing out an older copy of the page.<\/p>\n<p>Confirm it with one request. Load the page with a pointless query string on the end, such as a question mark followed by nocache=1. Most caches treat that as a new page. Then compare the two. If the query string version is clean and the normal one is not, you are looking at cache.<\/p>\n<p>Now clear the layers from your own server outwards. Cloudflare explains why the order matters. Update or remove the content at your origin before you purge it, because otherwise the next request simply caches the old version again. Purge the edge while your server still builds stale pages and you achieve nothing.<\/p>\n<p>Work through your layers in this order. Start with your caching plugin, using its clear-all option. WP Rocket, LiteSpeed Cache, W3 Total Cache, and WP Super Cache all have one. Note that WP Super Cache needs clearing in two places, both the admin bar and its settings page.<\/p>\n<p>Next clear your host&#8217;s cache. Most managed hosts have their own page cache, separate from any plugin. Kinsta, WP Engine, SiteGround, and Cloudways all provide a control for it in their own dashboards. Clear your object cache at the same time, if you run one. It holds query results. So it can keep old settings alive after a direct database edit.<\/p>\n<p>Then purge your CDN. On Cloudflare, that is under Caching and then Configuration. Cloudflare prefers that you purge single files by address rather than everything, to protect your performance. If you do purge everything, note that a successful response only confirms Cloudflare received the request. It does not confirm anything was removed.<\/p>\n<p>Finally clear your own browser. With developer tools open, long-press the reload button and choose to empty the cache and reload hard. That option only appears while developer tools are open.<\/p>\n<p>Clearing caches is safe. The only cost is a slower site for a few minutes while they refill.<\/p>\n<p>To verify, load the normal address with no query string, in a private window. The console should be clean. If you use Cloudflare, check that the cache status header reports a miss on your first request after purging. A slow but clean page is exactly what you want to see here. Our guide to <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-fix-page-speed-issues-in-wordpress-easily\/\">fixing page speed issues in WordPress<\/a> covers getting that speed back.<\/p>\n<h3>Step 9: Set Cloudflare to the right mode<\/h3>\n<p>This step addresses the Cloudflare cause. Skip it if you do not use Cloudflare or a similar proxy. If you do, it may be the root of everything above.<\/p>\n<p>Confirm your current mode first. Log into Cloudflare and open your SSL and TLS settings. Read the encryption mode. Newer accounts show Automatic as the default, with the named modes grouped under a custom option.<\/p>\n<p>Flexible is the mode to worry about. Cloudflare describes it directly. All connections between Cloudflare and your origin are made through plain http. That is why WordPress cannot tell the page is secure, and why you get mixed content on every single asset rather than only on old content.<\/p>\n<p>The right fix is to move to Full Strict. Cloudflare recommends it, and says that for the best security you should choose it whenever you can. It needs a valid certificate on your own server. Cloudflare will issue one free through its Origin CA if your host does not.<\/p>\n<p>Be aware of what Full Strict checks. The certificate must not be expired. It must come from a publicly trusted authority or from Cloudflare&#8217;s own Origin CA. And it must cover the hostname being requested. If any of those fail, visitors see a 526 error instead. So install the certificate first, then change the mode.<\/p>\n<p>Plain Full is not good enough as a destination. Cloudflare states that in Full mode the origin certificate is not validated in any way. It can be expired or self-signed. That leaves room for someone to intercept the connection between Cloudflare and your server.<\/p>\n<p>While you are there, know what the two helper features do. Always Use HTTPS redirects the page request only. Cloudflare says plainly that forcing HTTPS does not resolve mixed content. Automatic HTTPS Rewrites does rewrite links in the page. But it only rewrites a link once it has confirmed the file is reachable over https. And it only covers active content, unless your domain appears on the lists it consults. Passive content such as images is left alone.<\/p>\n<p>So treat both as a safety net, never as the fix. Cloudflare also recommends not performing redirects at your own server when you redirect at the edge, because doing both causes loops.<\/p>\n<p>Changing the encryption mode affects your live site immediately. Make the change when traffic is low, and have your certificate ready first.<\/p>\n<p>To verify, load the site in a private window and check the padlock. Then re-check the console on your most important pages. Purge the Cloudflare cache before testing, because a stale page will mislead you.<\/p>\n<h3>Step 10: Add the HTTP to HTTPS redirect properly<\/h3>\n<p>This step addresses the missing redirect cause. It is last for a reason. It will not fix mixed content, but without it visitors arriving on an http link never reach your secure page at all.<\/p>\n<p>Confirm whether you need it. Load your site deliberately over http. If the address bar switches itself to https, the redirect is already working. If the page loads and stays on http, you need one. You can also check from a terminal with a header request to the http address, and look for a permanent redirect in the response.<\/p>\n<p>If you use Cloudflare, do this at the edge. Turn on Always Use HTTPS in the Edge Certificates settings and stop there. Cloudflare recommends not also redirecting at your own server, because two redirects in two places cause loops.<\/p>\n<p>On an Apache server without a proxy, the rule goes in your .htaccess file. Apache&#8217;s own documentation gives this form for when you only have .htaccess to work with:<\/p>\n<pre><code>RewriteEngine On\r\nRewriteCond \"%{HTTPS}\" !=on\r\nRewriteRule \"^(.*)\" \"https:\/\/%{SERVER_NAME}$1\" [R=301,L]<\/code><\/pre>\n<p>Placement matters. Put it above the block marked BEGIN WordPress. WordPress rewrites everything between its own markers, so a rule placed inside them will disappear. Our guide to <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-set-up-and-fix-permalinks-in-wordpress\/\">setting up and fixing permalinks in WordPress<\/a> explains how that block works.<\/p>\n<p>There is one trap with this rule. Behind a proxy it does not work, and Apache says why. The HTTPS value asks the SSL module directly. If your certificate terminates upstream, that module is not handling the connection, so the value always reports off. In that case match on the forwarded protocol header instead, and only if you control the proxy.<\/p>\n<p>On Nginx, the official guidance is to use a return rather than a rewrite, in a server block listening on port 80. Nginx recommends the return directive because it stops processing immediately and is simpler.<\/p>\n<p>One more thing to protect. If you use an automatically renewed certificate, make sure your redirect does not block the renewal check. Let&#8217;s Encrypt recommends always allowing plain http access, with a redirect to https. Refusing port 80 outright is worse. Apache documents an exemption rule for the renewal path.<\/p>\n<p>Editing .htaccess can break your whole site. Copy the file first, so you can put it straight back.<\/p>\n<p>To verify, load your site over http and watch it switch to https. Then load a deep page the same way. Then confirm your padlock is still clean, because this step and mixed content are separate problems.<\/p>\n<h2>Best Practices to Prevent the WordPress Mixed Content Error in Future<\/h2>\n<p>Each habit below closes off one of the causes above. That is what makes them worth doing.<\/p>\n<p><strong>Install the certificate before the site goes live.<\/strong> This is the only habit that truly prevents the problem rather than cleaning it up. If https is on from the first day, no http address is ever written to your database. There is nothing to replace later, no packed settings at risk, and no builder files to regenerate.<\/p>\n<p><strong>Never hard-code an address in code.<\/strong> This closes off the hard-coded cause. Use the WordPress functions that build addresses for you, and load your assets through the enqueue functions. The Plugin Handbook is explicit that you should always use these functions instead of hard-coding paths. Never assume your uploads or themes sit in the default folder, because people move and rename them.<\/p>\n<p><strong>Make a dry run part of every migration.<\/strong> This closes off both database causes at once. After any move, restore, or staging push, run the search and replace dry run before you declare the job finished. It costs seconds and reports exactly how many http addresses are left. Treat a non-zero count as unfinished work.<\/p>\n<p><strong>Ship a content security policy as a safety net.<\/strong> Adding the <code>upgrade-insecure-requests<\/code> directive tells browsers to treat your insecure addresses as secure ones. MDN describes it as intended for sites with large numbers of insecure legacy addresses. Use it alongside the database fix, not instead of it. It fails closed, so a resource with no secure version still will not load, and it does nothing for inbound links from other sites.<\/p>\n<p>Do not reach for the old block-all-mixed-content directive. MDN marks it as deprecated and obsolete in the specification. Content that is not blocked is now always upgraded anyway, so the directive does nothing useful.<\/p>\n<p><strong>Add HSTS once you are confident.<\/strong> This closes off the inbound http link problem. The Strict-Transport-Security header tells browsers to only ever reach your site over https. Add it after everything works, because you cannot switch it off over an insecure connection. That is deliberate, and it means a rushed rollout is hard to undo.<\/p>\n<p><strong>Automate certificate renewal and watch the expiry.<\/strong> This closes off the certificate side of the problem. Let&#8217;s Encrypt certificates last ninety days by default, and the project states there is no way to extend that. It recommends renewing every sixty days, which is why automatic renewal matters. Monitor the expiry date too, so a failed renewal reaches you before it reaches your visitors.<\/p>\n<p><strong>Choose the right proxy mode and leave it alone.<\/strong> This closes off the detection cause for good. Aim for Full Strict on Cloudflare with a real certificate on your own server. Then redirect in one place only, either at the edge or at your server, never both.<\/p>\n<p><strong>Learn your cache layers now, not during an incident.<\/strong> This closes off the cache cause. Write down every layer you run and how to clear each one. Then remember the order: your own server first, the edge second, your browser last.<\/p>\n<p><strong>Re-check after anything that touches content at scale.<\/strong> This catches every cause coming back. A theme change, a builder update, a restored backup, or a new embed can all reintroduce an http address. Check the console on your key pages, or run a crawler. Tools such as Why No Padlock will check linked CSS files for insecure image calls, which is exactly the kind of thing a quick look misses.<\/p>\n<p>One last caution on tools. A certificate test such as Qualys SSL Labs or SSL Shopper checks your server configuration and your certificate installation. Neither looks inside your pages. A perfect certificate score tells you nothing at all about mixed content.<\/p>\n<h2>Conclusion<\/h2>\n<p>A broken padlock after an SSL switch looks alarming. In practice it is a narrow problem with a short list of causes and a clear order of fixes.<\/p>\n<p>Start by confirming the symptom. The page loaded over https, the browser says Not secure, and the console shows messages beginning with Mixed Content. Separate that from a certificate warning, a redirect loop, or plain broken images, because each of those needs a different guide.<\/p>\n<p>Then remember what the browser is doing. Images, audio, and video are upgraded automatically and only fail if no secure version exists. Everything else is blocked outright, with no warning and no fallback. That is why a missing stylesheet wrecks your layout while a missing image merely looks untidy.<\/p>\n<p>The causes fall into clear groups. Your two site addresses. WordPress not detecting the secure connection. Old links in content. Old links in packed settings. Page builder data and its generated files. Addresses written into code. Third-party services with no secure version. Caching. Cloudflare&#8217;s modes and limits. And a redirect that was never the fix people hoped it was.<\/p>\n<p>Work the steps in order and each one earns its place. Fix your addresses and your detection first, because everything downstream inherits them. Then clean your content, your packed settings, and your builder data with tools that understand the format. Then handle code, third parties, caches, your proxy mode, and finally your redirect. Every step tells you how to confirm the cause is yours and how to check your fix held.<\/p>\n<p>Keep the prevention habits as well. HTTPS from day one. No hard-coded addresses. A dry run after every migration. A content security policy as a net, HSTS once you are sure, and automatic certificate renewal. Those few habits mean you clean this up once and never again.<\/p>\n<p>If the same site move also locked you out of your dashboard, that is a known companion problem. Read our guide on <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-admin-redirecting-to-homepage\/\">fixing WordPress admin redirecting to the homepage<\/a>.<\/p>\n<p>For the official reference material, see <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/Security\/Defenses\/Mixed_content\" target=\"_blank\" rel=\"noopener\">MDN&#8217;s documentation on mixed content<\/a> and the WordPress <a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/security\/https\/\" target=\"_blank\" rel=\"noopener\">handbook page on HTTPS<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction You installed your SSL certificate. You switched the site to https. You expected a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4449,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[573,574,575,571,572],"class_list":["post-4432","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-https-migration","tag-not-secure-warning","tag-ssl-troubleshooting","tag-wordpress-mixed-content","tag-wordpress-ssl"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Fix the WordPress Mixed Content Error After SSL<\/title>\n<meta name=\"description\" content=\"Padlock gone after switching to HTTPS? Learn what causes the WordPress mixed content error, and fix every source of it with safe, step-by-step checks.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Fix the WordPress Mixed Content Error After SSL\" \/>\n<meta property=\"og:description\" content=\"Padlock gone after switching to HTTPS? Learn what causes the WordPress mixed content error, and fix every source of it with safe, step-by-step checks.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/\" \/>\n<meta property=\"og:site_name\" content=\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting &amp; Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-26T07:50:12+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-26T08:07:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Mixed-Content-Error-After-SSL-1024x576.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"576\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"James\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"James\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"29 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/\"},\"author\":{\"name\":\"James\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/person\\\/42bec463c3b7b14c88f4c787a7009730\"},\"headline\":\"How to Fix WordPress Mixed Content Error After SSL\",\"datePublished\":\"2026-10-26T07:50:12+00:00\",\"dateModified\":\"2026-10-26T08:07:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/\"},\"wordCount\":6474,\"publisher\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/WordPress-Mixed-Content-Error-After-SSL.png\",\"keywords\":[\"HTTPS migration\",\"not secure warning\",\"SSL troubleshooting\",\"WordPress mixed content\",\"WordPress SSL\"],\"articleSection\":[\"WordPress\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/\",\"name\":\"How to Fix the WordPress Mixed Content Error After SSL\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/WordPress-Mixed-Content-Error-After-SSL.png\",\"datePublished\":\"2026-10-26T07:50:12+00:00\",\"dateModified\":\"2026-10-26T08:07:24+00:00\",\"description\":\"Padlock gone after switching to HTTPS? Learn what causes the WordPress mixed content error, and fix every source of it with safe, step-by-step checks.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/WordPress-Mixed-Content-Error-After-SSL.png\",\"contentUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/WordPress-Mixed-Content-Error-After-SSL.png\",\"width\":2560,\"height\":1440,\"caption\":\"WordPress Mixed Content Error After SSL\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-mixed-content-error-after-ssl\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Fix WordPress Mixed Content Error After SSL\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\",\"name\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\",\"name\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/logo__1_-removebg-preview.png\",\"contentUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/logo__1_-removebg-preview.png\",\"width\":600,\"height\":226,\"caption\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/person\\\/42bec463c3b7b14c88f4c787a7009730\",\"name\":\"James\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"caption\":\"James\"},\"description\":\"James is an experienced WordPress and WooCommerce specialist with over 10 years of practical experience. At WPChatSupport, he creates clear guides that help website owners fix WordPress issues, improve speed, secure their sites, and manage WooCommerce stores with confidence. His expertise includes store setup, plugin configuration, theme customization, payment gateway integration, and website troubleshooting. Through simple and helpful content, James supports users in solving technical problems and following best practices for online business growth.\",\"sameAs\":[\"https:\\\/\\\/blog.wpchatsupport.com\"],\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/author\\\/24x7wpsupport\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Fix the WordPress Mixed Content Error After SSL","description":"Padlock gone after switching to HTTPS? Learn what causes the WordPress mixed content error, and fix every source of it with safe, step-by-step checks.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/","og_locale":"en_US","og_type":"article","og_title":"How to Fix the WordPress Mixed Content Error After SSL","og_description":"Padlock gone after switching to HTTPS? Learn what causes the WordPress mixed content error, and fix every source of it with safe, step-by-step checks.","og_url":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/","og_site_name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting &amp; Tutorials","article_published_time":"2026-10-26T07:50:12+00:00","article_modified_time":"2026-10-26T08:07:24+00:00","og_image":[{"width":1024,"height":576,"url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Mixed-Content-Error-After-SSL-1024x576.png","type":"image\/png"}],"author":"James","twitter_card":"summary_large_image","twitter_misc":{"Written by":"James","Est. reading time":"29 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/#article","isPartOf":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/"},"author":{"name":"James","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/person\/42bec463c3b7b14c88f4c787a7009730"},"headline":"How to Fix WordPress Mixed Content Error After SSL","datePublished":"2026-10-26T07:50:12+00:00","dateModified":"2026-10-26T08:07:24+00:00","mainEntityOfPage":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/"},"wordCount":6474,"publisher":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/#primaryimage"},"thumbnailUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Mixed-Content-Error-After-SSL.png","keywords":["HTTPS migration","not secure warning","SSL troubleshooting","WordPress mixed content","WordPress SSL"],"articleSection":["WordPress"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/","url":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/","name":"How to Fix the WordPress Mixed Content Error After SSL","isPartOf":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/#primaryimage"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/#primaryimage"},"thumbnailUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Mixed-Content-Error-After-SSL.png","datePublished":"2026-10-26T07:50:12+00:00","dateModified":"2026-10-26T08:07:24+00:00","description":"Padlock gone after switching to HTTPS? Learn what causes the WordPress mixed content error, and fix every source of it with safe, step-by-step checks.","breadcrumb":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/#primaryimage","url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Mixed-Content-Error-After-SSL.png","contentUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Mixed-Content-Error-After-SSL.png","width":2560,"height":1440,"caption":"WordPress Mixed Content Error After SSL"},{"@type":"BreadcrumbList","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-mixed-content-error-after-ssl\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.wpchatsupport.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Fix WordPress Mixed Content Error After SSL"}]},{"@type":"WebSite","@id":"https:\/\/www.wpchatsupport.com\/blog\/#website","url":"https:\/\/www.wpchatsupport.com\/blog\/","name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials","description":"","publisher":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.wpchatsupport.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization","name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials","url":"https:\/\/www.wpchatsupport.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2025\/07\/logo__1_-removebg-preview.png","contentUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2025\/07\/logo__1_-removebg-preview.png","width":600,"height":226,"caption":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/person\/42bec463c3b7b14c88f4c787a7009730","name":"James","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","caption":"James"},"description":"James is an experienced WordPress and WooCommerce specialist with over 10 years of practical experience. At WPChatSupport, he creates clear guides that help website owners fix WordPress issues, improve speed, secure their sites, and manage WooCommerce stores with confidence. His expertise includes store setup, plugin configuration, theme customization, payment gateway integration, and website troubleshooting. Through simple and helpful content, James supports users in solving technical problems and following best practices for online business growth.","sameAs":["https:\/\/blog.wpchatsupport.com"],"url":"https:\/\/www.wpchatsupport.com\/blog\/author\/24x7wpsupport\/"}]}},"_links":{"self":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4432","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/comments?post=4432"}],"version-history":[{"count":2,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4432\/revisions"}],"predecessor-version":[{"id":4448,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4432\/revisions\/4448"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/media\/4449"}],"wp:attachment":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/media?parent=4432"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/categories?post=4432"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/tags?post=4432"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}