Forum Moderators: phranque

Message Too Old, No Replies

SSL problem with Firefox but not with IE

         

gpilling

11:12 pm on Jul 21, 2009 (gmt 0)

10+ Year Member



I was setting up a new PC in the office today and I got a rude surprise. The new ecommerce site that I have been working on flashed up a "untrusted connection" warning in Firefox (version 3.5.1). I have an SSL from GoDaddy.

The error message is:
"www.example.com uses an invalid security certificate.
The certificate is not trusted because the issuer certificate is unknown.
(Error code: sec_error_unknown_issuer)"

Also when I went to login to the server using Nodeworx it gave me this message:
"example.com:2443 uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
The certificate is only valid for interworx.info
(Error code: sec_error_untrusted_issuer)"

Using the site in IE6 there is no problems and I can purchase a product just fine - there is a little gold padlock, the browser says https:

I tried it with Google Chrome - no problems.

So can anyone shed some light on this?

LifeinAsia

11:28 pm on Jul 21, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



I believe you have to go through another step when adding a certificate from GoDaddy. See their site and follow the installation instructions to the letter.

Yes, it's more of a pain to install than a cert from Network Solutions. But for the annual savings? Yeah, I'll jump through a few more hoops!

rocknbil

2:33 pm on Jul 22, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The certificate is not trusted because it is self-signed....

I tried it with Google Chrome - no problems.

You might check your browser settings, the warnings for untrusted certs are probably unchecked/disabled.

I'm no expert on SSL but a self-signed cert is one created on the server without verification by a certificate authority. That is, anyone (with the know-how) can generate an SSL cert on a server and have it encrypt data to and from the browser (which is the primary function of SSL.) So your self-signed cert is encrypting, it's just not "known."

A cert becomes trusted if it's verified by the cert authority, that is, the issuer (goDaddy) recognizes it and their fingerprint is installed in the .crt bundle properly.

If you have a dedi/VPS (and possibly shared hosting), there should be an area in the control panel of your domain where you paste both the cert and the bundle .crt, or just upload them (easiest so the cert doesn't get munged by your editor.) You unzip the cert, upload/paste the two .crt files, on success when you check the "lock" icon on the site, it should have the valid expiration date and "trusted by (goDaddy's cert authority)".

All of the above are paraphrased/generic explanations, as I said I'm no expert but that is the gist.

This actually makes it easier, in most environments an admin has to do the install via command line.

The certificate is only valid for interworx.info

Note that a cert can only be bound to a single exact domain name. you would need two certs for example.com and www. example.com (I'm sure there are special certs for multiple names, and there is a "shared cert" for many domain names - much more expensive.)

gpilling

11:59 am on Jul 24, 2009 (gmt 0)

10+ Year Member



It is fixed now. I had only installed half of it I guess - oh well live and learn.

LifeinAsia

3:09 pm on Jul 24, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



It is fixed now.

Great!

oh well live and learn

That's what life is all about! :) Unfortunately, so many people go through life without doing much of either (living and learning)...