When I type: https://www.misslenacoco.com, I can see that your site has https enabled, but it’s still not secure. If you are running a self hosted site on a general hosting plan somewhere in the world, then you’re responsible for fixing “insecure content” errors.
I can see in the javascript console of Google Chrome’s developer tools that you have insecure content errors. See the screenshot here: https://cloudup.com/cfvtVhZftew
What that means, is that you uploaded your original images under your http version of the site and the path to the images is still https and not https.
For example, in the past, you may have uploaded image1.jpg. So the path is http://mysite.com/wp-content/uploads/2013/01/image1.jpg. Because you uploaded the image already, it’s difficult to change the prefix of the path from http to https.
To fix “mixed content” errors, you can use a plugin called SSL Insecure Content Fixer. This plugin will help convert https to https for all previously uploaded images. There are various settings for the plugin, so if you need help, please contact that plugin author.
Once you install and activate this plugin, then update it’s settings under Dashboard > Settings and you find the reference to the plugin, it should resolve your mixed content errors and you should see the green lock to let you know your site is secure.
Hope that helps.
-
This reply was modified 7 years, 2 months ago by
Tony Zeoli. Reason: add tag "mixed content errors"
Additionally, if you mean that you want the HTTP version to automatically redirect to the HTTPS version, add this to your .htaccess file:
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]