If you do not see the secure lock in your browser address bar, you still have mixed content. It is very important that this is fixed, because browsers will throw all sorts of warnings at users, who might get scared.
What is mixed content?
How can I fix the mixed content on my WordPress website?
If the mixed content fixer is active, but you still don’t have the green lock, you have a type of mixed content that can’t be fixed automatically:
Some .css or .js files contain hard coded http links, which will cause mixed content warnings. For example if you use a theme that generates custom css with hardcoded http links, this will cause mixed content warnings.
- Hot linked images
If you have embedded an image on your domain, domain-1.com and the URL to that image is domain-2.com, and domain-2 does not have an SSL certificate, this image will be blocked by the browser.
These will get fixed by Really Simple SSL, but again, if the remote domain does not have an SSL certificate, these files can’t get loaded over https.
- Included js or css files on other domains, and this domain does not have an SSL certificate
If you include files from another domain, this domain also needs to have an SSL certificate.
- http links in css or js files on other domains
If the remote files can get loaded over https, but contain hardcoded http links (which happens a lot) mixed content warnings are the result.
These links can be located in theme files, plugins, or maybe in a widget you inserted on your site. Sometimes images are inserted from another website with that website’s URL, which won’t work anymore if that URL can’t load on SSL.
To find these issues, you might consider buying the Really Simple SSL pro plugin, which scans your entire site for all possible issues in files and database, and creates a list of issues to fix and when possible it offers a “fix” option. If not, you’ll get instructions how to fix it. For example, the plugin can’t fix a hot linked image if the image doesn’t exist, or if the remove server blocks the downloading. Besides this, you get added options that improve your security, like HTTP Strict Transport Security, the preload list, a certificate expiration warning option, mixed content fixer for the admin, and more.
If you want to do this manually:
First, check if the mixed content fixer is active.
If it is, you’ll have to track down the urls that were not fixed automatically.
- Clear any cache in your browser, by clearing the history
- If you have a caching plugin active, clear the cache and check if it has been cleared.
Still getting mixed content warnings? Follow these steps:
Find the warnings in the console
Open your site in Google Chrome,
Right click on your website. A drop down will appear, with an option “inspect”
When you click this option “inspect”, part of your browser changes into a development screen:
To enter the console, simply click “Console”. Then you will see the mixed content warnings, like:
Mixed Content: The page at ‘https://domain.com’ was loaded over HTTPS, but requested an insecure image ‘http://domain.com/…’. This content should also be served over HTTPS. A mixed content warning will always show ‘Mixed content’. Other warning can be ignored for mixed content purposes.
Now we are getting somewhere! In the yellow/red characters, you will find some links. These links are the cause of your frustrations. How to fix them depends on your theme, plugins, etc.
Trace back the mixed content warnings to the origin
In most cases the mixed content fixer in Really Simple SSL will fix all issues in your HTML, so we can expect most issues to be in the resources. Usually if the site doesn’t have a secure lock right away, and the mixed content is coming from your own domain the issue is caused by caching. Clearing all caches the website uses usually resolves mixed content issues. If your site uses Elementor or Divi you might have to perform some additional steps before your site becomes fully secure. See the respective articles for instructions (Elementor, Divi).
Development console advanced search
The development console offers an advanced search feature to determine the origin of the mixed content. On a mac, press option + command + F to open this feature. On Windows, press Ctrl + Shift +F. When pressed, a small search box will appear:
In this box you can copy the url of the image we have previously identified as causing mixed content. Pressing enter will do a search and show more information about the location of the image. This search will usually find mixed content in .css and .js files too.
Some mixed content cannot be found by the advanced search. To manually find the cause of the mixed content, right click on the page and click on “view source”.
If we click “view source”, we now see the html code of the page. Do a search (ctrl F or cmd F) on the insecure link you found in the previous steps.
If the link is not in the source, it is probably located in a .css or .js file, generated by a plugin or your theme. Check all your plugins, re-save the options, and do the same with your theme.
To find mixed content in your css or js, you can also download these files from your server, do a search on the insecure URL, and replace any http links you might find.
Of course, you can also save yourself some time and buy the premium plugin, which offers the scan which does all this automatically, and offers secure cookie setting, HSTS, SSL expiration warning, and includes premium support as well.