Real Reviews By Me!
SEO Tips and Tricks!
The good, the bad, the ugly!

Installed SSL But Still Getting Insecure Warnings!

Aghhh SSL! Good times right? Eh….

ssl-site-insecureSo you paid for the SSL…. they installed it, but when you go to your site you are seeing something like this. “Your connection to this site is not fully secure” or “connection not private”.

I am gonna base this off a wordpress install because that is pretty much what most people do and what I do on all my sites.

One thing you will want to do is add a plugin like Really Simple SSL https://wordpress.org/plugins/really-simple-ssl/

I’ve used this on countless sites and it works great! It basically makes a lot of the behind the scene changes for you so everything on your site is now using https

But… you are still getting insecure connection warnings.

FIRST GO HERE:

https://www.whynopadlock.com/check.php & enter your domain and let it scan. If there is something that is not using https it will show you. Now you simple have to go and find out where it is and update it to https

Here is a hint…. it will most likely be some sort of custom CSS you may have added in your theme at some point

WHY SSL?

There are a lot of reasons these days… Google likes its… most browsers are now letting visitors know that your site is not secure on any parts they have to enter an email address. Your site can run faster… more secure… tons of stuff.

The simple of it is get your site on SSL! Don’t get ripped off either. Some places like GODADDY will rip you off big time!!

I host 90% of my sites on SITEGROUND and they use Let’s Encrypt which is FREE and super easy. You basically login to your cpanel click on Let’s Encrypt and bamm your site is now has an SSL. Just make sure to do the stuff I mentioned above. You can CLICK HERE to check out Sitegrounds hosting which I highly recommend!

2 Comments

  1. PikaPika on October 28, 2017 at 2:21 pm

    Yes!! You da man! This was driving me nuts! That really simple ssl plugin helped and the why no padlock site showed me exactly what the issue was. Was actually the same thing. A hard coded line in my CSS. Changed that to https and good to go. Thanks again!! Lifesaver!!

    • mrwhackahost on November 7, 2017 at 9:24 pm

      Hey no problem glad I could help. Nothing more frustrating then something silly messing you up, but it is even better when you find the solution!

Leave a Comment