Fixing Insecure Content After SSL Integration
One of the issues that we encounter when we either migrate a website from HTTP to HTTPS, or we just add an SSL certificate to a website, is that some of the items may actually be hard coded as HTTP, With the Oshine Tatsu theme, the one that this site was built with, it’s a common issue, so we’re going go through this and I’m going to show you really quickly how we’re going to fix this. It’s really not that hard.
Whynopadlock.com to Find What’s Insecure
We’re going to take this URL, we’re going to go to a website called whynopadlock.com. We’re going to enter that URL right there, and it’s actually going to identify all of the assets on the page that are referring to something that’s HTTP and not HTTPS. I’m going to click edit. We’re going to go down and replace the images that are, or the assets that are HTTP. I kind of had a little Freudian slip here. We virtually always have issues with images when it comes to this theme, so we’re looking at the iPhone images, HTTP, so we’re going to click on this. All I’m going to do is X that out, and we’re going to replace it with a new image and hit save.
Test to Ensure it’s Fixed
Then, from there we’re just going to retest it, and it looks like everything has been resolved. This last step, we’re going to take a look at the actual page, we’re going to view the page here, and there we have that little green lock. So, fairly straightforward. Usually the culprit, again, are images on the page, but sometimes you may actually have it referring to something else as well, and usually, it very easily remedied.