Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : SSL Problem

[Shikhir A]

I have purchased a SSL from Geocerts, a Geotrust SSL reseller. They are 100% good certificates and show up as Geotrust issued certificates. The domain on the cert is a www.domain.com - but it only works on some browsers. It works on the newest Firefox and Safari and newest IE (IE8+) but not the Google Chrome browser, anything like Firefox 3.4 or below, etc..although it is an EV SSL and it should work fine (trusted issuer). It says that "some of the content on the page is insecure."

Perhaps it is a way I installed it (I requested a cert request file/generated one from cPanel and then pasted that into the Geocerts panel and got a Certificate which I pasted into the cPanel SSL install wizard and it automatically got the domain/IP/request file).

.cer file download:

http://www.uploadsafe.com/uploads/do...be6347baf5bfba


Thanks in advance

[poetren]

I think (and this could be off) that when it says some of the content on the page is insecure, it's because you have links from your page to http:// links rather than every link going to a secure url. We had this with a wildcard cert when we had a live chat that was an http:// link, once we removed that, it no longer said any of the content was insecure on our domain.

[Shikhir A]

Originally Posted by poetren

I think (and this could be off) that when it says some of the content on the page is insecure, it's because you have links from your page to http:// links rather than every link going to a secure url. We had this with a wildcard cert when we had a live chat that was an http:// link, once we removed that, it no longer said any of the content was insecure on our domain.

But I tried going to https://www.domain.com/fasfaf and it returned a 404 (fine as we don't have that directory), some browsers (as I said above) showed the cert fine but the rest said the same thing (on a 404 page).

[Hostify Networks]

Did you change all the links to images, scripts, etc on your https page to https? If not, there's your issue. If you think you did, then go back and check because you missed something.

For example...suppose you are at https://example.com and this page loads an image called "image.png." You would have <img src="https://example.com/image.png" alt="" /> rather than <img src="http://example.com/image.png" alt="" />

Another example, if you go to https://hostify.me/ you'll get the same message concerning some things on the page not being secure. This is because the images are using http rather than https (not sure how that got reverted...but I'll leave it that way for the time being).

It would be helpful to know the domain...then I could tell you exactly what's wrong.

[Shikhir A]

Originally Posted by pvcsnathan

It would be helpful to know the domain...then I could tell you exactly what's wrong.

https://www.vlexo.com/

[Hostify Networks]

Okay, that helps. The only obvious thing I see is the Adsense. Adsense doesn't support https (unless they've changed that recently).

[ServerManagement]

Please check to make sure the CABundle is installed properly, this can cause some browser recognition to fail if you are seeing errors only in some browsers and not others.

Also, check the image/css/js links in the page too, this can also cause the error that says some objects on the page are not secure.

[Shikhir A]

How do we check the CABundle?

Second, https://www.vlexo.com/testifks

no adsense, yet error.

Originally Posted by ServerManagement

Please check to make sure the CABundle is installed properly, this can cause some browser recognition to fail if you are seeing errors only in some browsers and not others.

Also, check the image/css/js links in the page too, this can also cause the error that says some objects on the page are not secure.

[Hostify Networks]

OH, one obvious thing I missed... After rereading your first post, it appears that you did WWW.domain.com. This is DIFFERENT from domain.com. If you want to cover both, you will need a wildcard cert (or simply redirect everything to www.domain.com). Note that the same thing happens for me: https://hostify.me/ https://www.hostify.me/

I've tried in Chrome, IE6, IE8, and Firefox. For whatever reason, Firefox doesn't seem to be very happy about it but all the other browser recognize the cert and appear to work as intended. Speaking of IE6, you'll want to check your site in it...you'll probably want to add some code to take care of the transparency issues it has with png.

[Shikhir A]

But I am going to https://www.

..not https://___

and also, FF is a very common browser, so it should recognize
it..

I don't think I need a Wildcard.

Originally Posted by pvcsnathan

OH, one obvious thing I missed... After rereading your first post, it appears that you did WWW.domain.com. This is DIFFERENT from domain.com. If you want to cover both, you will need a wildcard cert (or simply redirect everything to www.domain.com). Note that the same thing happens for me: https://hostify.me/ https://www.hostify.me/

I've tried in Chrome, IE6, IE8, and Firefox. For whatever reason, Firefox doesn't seem to be very happy about it but all the other browser recognize the cert and appear to work as intended. Speaking of IE6, you'll want to check your site in it...you'll probably want to add some code to take care of the transparency issues it has with png.

[Hostify Networks]

Firefox seems to be a bit more particular about certs. A little bit of Google came up with this: https://support.comodo.com/index.php...articleid=1249