# Verisign ssl certificate issue

**URL:** <https://www.ruby-forum.com/t/verisign-ssl-certificate-issue/174858>\
**Category:** NGINX\
**Created:** [September 3, 2009, 6:05am UTC](https://www.ruby-forum.com/t/verisign-ssl-certificate-issue/174858 "2009-09-03T06:05:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![iberci](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/a3d4f5/32.png) [@iberci](https://www.ruby-forum.com/u/iberci)\
**Post date:** [September 3, 2009, 6:05am UTC](https://www.ruby-forum.com/t/verisign-ssl-certificate-issue/174858/1 "2009-09-03T06:05:58Z")

</div>

We recently switched from GoDaddy SSL certificate to Verisign’s.  
Installation on Nginx went well.

Some users and browsers are reporting that the “certificate was signed  
by an  
unknown authority”.

You can try this by going to [https://www.spellingcity.com](https://www.spellingcity.com).

It doesn’t seem that we had this issue with the GoDaddy certificate…  
is  
there anything else I need to do with Nginx SSL configuration to make  
this  
issue “go away” or is this strictly a Verisign issue (I am contacting  
them  
as well).

Thanks

---

<div class="post-metadata">

**Author:** ![iberci](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/a3d4f5/32.png) [@iberci](https://www.ruby-forum.com/u/iberci)\
**Post date:** [September 3, 2009, 7:38am UTC](https://www.ruby-forum.com/t/verisign-ssl-certificate-issue/174858/2 "2009-09-03T07:38:31Z")

</div>

On Wed, Sep 02, 2009 at 11:59:28PM -0400, Ilan B. wrote:

> We recently switched from GoDaddy SSL certificate to Verisign’s.  
> Installation on Nginx went well.
> 
> Some users and browsers are reporting that the “certificate was signed by an  
> unknown authority”.

What browsers ?

> You can try this by going to [https://www.spellingcity.com](https://www.spellingcity.com).
> 
> It doesn’t seem that we had this issue with the GoDaddy certificate… is  
> there anything else I need to do with Nginx SSL configuration to make this  
> issue “go away” or is this strictly a Verisign issue (I am contacting them  
> as well).

Currently you have this cert chain:

openssl s\_client -connect www.spellingcity.com:443

* * *

Certificate chain  
0 s:/C=US/ST=Florida/L=Fort Lauderdale/O=[SpellingCity.com](http://SpellingCity.com),  
Inc./OU=Terms of use at [www.verisign.com/rpa](http://www.verisign.com/rpa)  
(c)05/CN=[www.spellingcity.com](http://www.spellingcity.com)  
i:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at  
[https://www.verisign.com/rpa](https://www.verisign.com/rpa) (c)09/CN=VeriSign Class 3 Secure Server CA

- G2  
1 s:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at  
[https://www.verisign.com/rpa](https://www.verisign.com/rpa) (c)09/CN=VeriSign Class 3 Secure Server CA
- G2  
i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification  
Authority - G2/OU=(c) 1998 VeriSign, Inc. - For authorized use  
only/OU=VeriSign Trust Network

* * *

---

<div class="post-metadata">

**Author:** ![iberci](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/a3d4f5/32.png) [@iberci](https://www.ruby-forum.com/u/iberci)\
**Post date:** [September 3, 2009, 7:42am UTC](https://www.ruby-forum.com/t/verisign-ssl-certificate-issue/174858/3 "2009-09-03T07:42:37Z")

</div>

Thanks Igor, problem solved, turns out I needed to add the Verisign  
intermediate key.

2009/9/3 Igor S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![iberci](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/a3d4f5/32.png) [@iberci](https://www.ruby-forum.com/u/iberci)\
**Post date:** [September 3, 2009, 1:24pm UTC](https://www.ruby-forum.com/t/verisign-ssl-certificate-issue/174858/4 "2009-09-03T13:24:30Z")

</div>

I believe that’s correct.

---

<div class="post-metadata">

**Author:** ![iberci](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/a3d4f5/32.png) [@iberci](https://www.ruby-forum.com/u/iberci)\
**Post date:** [September 3, 2009, 8:18am UTC](https://www.ruby-forum.com/t/verisign-ssl-certificate-issue/174858/5 "2009-09-03T08:18:54Z")

</div>

On Thu, Sep 03, 2009 at 01:36:39AM -0400, Ilan B. wrote:

> Thanks Igor, problem solved, turns out I needed to add the Verisign  
> intermediate key.

So before you chain was just:

0 s:/C=US/ST=Florida/L=Fort Lauderdale/O=[SpellingCity.com](http://SpellingCity.com), Inc./OU=Terms  
of use at [www.verisign.com/rpa](http://www.verisign.com/rpa) (c)05/CN=[www.spellingcity.com](http://www.spellingcity.com)  
i:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at  
[https://www.verisign.com/rpa](https://www.verisign.com/rpa) (c)09/CN=VeriSign Class 3 Secure Server  
CA - G2

?
