- This topic has 9 replies, 1 voice, and was last updated 6 years, 10 months ago by
.
-
Posts
-
I finally got our host to add an SSL certificate to my adult blog but for some reason this is still showing “insecure connection” in FireFox. I’ve tried to check it out in other browsers but to be honest I’m a little lost when it comes to checking it in others.
Checking from other sources says it’s there and working, but I really don’t know.
When I actually physically type in https for the domain it leads to a fucked up view of the site.Can anyone else out there check it out for me on whatever you’re using and see what happens?
It would really help me out before I get back to our host and scream at them some more.
Just converting the page doesn’t do anything meaningful. You have to convert everything on the page. Do a “view source” and look for all instances of http:// and get them converted to https:// – Or better yet, have them start with / or // where possible.
Bottom line you’ve taken the first step in a many step process. Keep going.
Thanks DOC.
Nothing is ever simple in this business.
You have to search all http :// and replace with https ://
This needs SQL execution on datebase. Back up everything before you start.My hosting company is also trying to convince me to switch my adult site to https. I told them I will stay with http because:
1) I don’t collect user info and I do not deal with billing transaction. There is no need to build up a SSL connection bewteen end users and my blog.
2) Most embedded videos from sponors still use http ://. If I switch my site to https, I will get countless warnings as I have http and https urls mixed in same page.Just my 2 cents.
Thanks.
I did a little test and created a new test page on the server with SSL urls and it was still not showing as secure.
So, it seems that even if I did go through the process of changing every url this would not resolve the issue.One of these two statements is not true:
I did go through the process of changing every url
it was still not showing as secureIf all the elements on a page are HTTPS, the lock will show.
That’s not what I said.
I stated that I created a test page. Entirely separate from the blog. I did not state that I changed every URL (hence creating a “test” page).
The test page was a simple html page created from scratch with test images and content with every URL on the page https.
The lock did not display.Give me the URL of your test page and I will show you that there is something that is still not HTTPS.
It’s already been deleted.
If I create another one I’ll let you know.
It turns out we were both wrong!
It was all down to Securi and their settings for the site.
After going through a few things with them and changing some core settings everything seems to be working fine
