Hi All
I'm having a problem once I've imported my SSL certificate and then try and browes to my site I get the following error in firefox "sec_error_unknown_issuer" and in IE it gives me a totaly differant certificate issued to *.apphb.com.
Can anyone help me with this?
Thanks
Kevin
#1 Posted by rune Support staff on 10 May, 2011 05:21 AM
Hi Kevin,
That sounds interesting. It may be related to SNI SSL not being supported by your browser and/or operating system. Since you experience it in multiple browser I wonder if you may be running Windows XP?
Otherwise please let me know which application it is and we'll take a closer look at it.
Best,
Rune
rune closed this discussion on 10 May, 2011 05:21 AM.
kevin.turnbull re-opened this discussion on 10 May, 2011 07:23 AM
#2 Posted by kevin.turnbull on 10 May, 2011 07:23 AM
Hi Rune
I've been testing this with an XP and windows 7 PC
Thanks
Kevin
#3 Posted by rune Support staff on 10 May, 2011 11:28 PM
SNI SSL has very limited support for Windows XP, but it should work in most browser on Windows 7. Could you give me the application name so I can take a look at it?
Thanks,
Rune
#4 Posted by kevin.turnbull on 11 May, 2011 08:44 AM
the application it loot, site www.loot2012rentals.com
thanks
Kevin
#5 Posted by rune Support staff on 11 May, 2011 06:57 PM
Chrome redirected me to the non-https site without any warnings, but I can see the same issue as you're having in Firefox. I think it's related to the issuer of your certificate not being recognized by the browser - and I can see that other's have had issues with "Comodo CA Limited" in the past (http://stackoverflow.com/questions/275878/firefox-and-ssl-sec-error...). Perhaps the solution suggested there works?
They're suggesting chaining certificates among other things. To do that you can simply insert the certificate from your CA (that you probably received when you got the certificate) and insert that above your own certificate in the "Public Key" field when creating a certificate.
Also, the issue where you got the .apphb.com certificate in IE is related to that version of IE (or because it's running on XP) not supporting SNI - this means that it falls back to the default certificate, which on our load balancers are the .apphb.com certificates. You can use that for piggyback ssl if you'd like :-)
rune closed this discussion on 11 May, 2011 06:57 PM.