Hello,
You can investigate what is causing your mixed content errors by using the browser console, most browsers you can use ctrl shft i to open and select the console.
I couldn’t see any errors on the link you posted there, but found one here:
The reason for the error on this page is there is an image which is being loaded over https:
Since you have SSL on the domain, you should be able to load anything over SSL from your server.
Personally, my process for switching sites to SSL is to use this plugin:
And then follow this process:
- Back up the database
- Run a search replace, with all three options checked – i.e. case insensitive, replace GUIDs and Run as Dry Run, replacing http://blondiesstl.com with https://blondiesstl.com
- Assuming no errors occur you should get a confirmation and summary of the number of cells found to change but 0 changes made
- Re-run the search replace with Run as Dry Run deselected
This should replace any references in your database to resources on your server with http:// to https:// and remove any errors.
Other options you can explore are:
- Any options your host may offer to automatically forward any http requests to https
- Run your website through CloudFlare who provide free SSL and also offer options for auto-forwarding to https
Hope that helps.
Moderator
t-p
(@t-p)
I don’t if you already have, try reviewing this tutorial: https://www.wpbeginner.com/plugins/how-to-fix-the-mixed-content-error-in-wordpress-step-by-step/
Also try clearing all cache (plugins, browser,server…).
Thread Starter
itseno
(@itseno)
@dominic_ks Thank you for the help. We tried running the better search replace plugin and were able to change a good amount of the site’s http to https requests.
The search with the following: http://blondiesstl.com%26/#8221 did not result in any items, it said 0 cells found and 0 changes made.
We called our hosting provider as well, Hostek, to discuss automatically forwarding any http requests to https, but even when we changed the .htaccess to accomplish this, no results:
# Only trigger rule if a non-ssl port is being used
RewriteCond %{SERVER_PORT} !443
# Redirect to HTTPS
RewriteRule (.*) https://www.example.com/$1 [R=301]
Finally, we explored Cloudflare, but we have our own dedicated SSL, so we aren’t sure how Cloudfare would interact with our site.
Do you have any additional advice?
Hello,
I don’t know where some of those characters came from, you’re just looking to search this:
And replace with this:
i.e. replace instances of your site url that only has http with https.
I’m not very big on using .htaccess manually for this purpose, but couldn’t help but notice that your pasted code had example.com in it, I assume you changed it for your own domain…?
CloudFlare – yes the idea here is that you use their SSL certificate rather than your own, but just looks like you’re using a regular free LetsEncrypt certificate? If so, I have found that they work as well as each other.