> ## Content Index
> Fetch the complete content index at: https://helpmonks.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Nginx, Apache, SSL and signed by an unknown certifying authority
- URL: https://helpmonks.com/blog/nginx-apache-ssl-and-signed-by-an-unknown-certifying-authority/
- Published: 2010-01-17T00:00:00.000Z
- Updated: 2026-04-06T20:07:48.000Z
- Description: We just moved a whole bunch of servers to a new hosting center and moved from CentOS (more on this in a later blog post). While we migrated mostly everything
- Author: Nitai
- Tags: email marketing

We just moved a whole bunch of servers to a new hosting center and moved from [CentOS](http://www.centos.org/?ref=helpmonks.com) to [Ubuntu](http://www.ubuntu.com/?ref=helpmonks.com) (server) and Apache to [Nginx](http://wiki.nginx.org/?ref=helpmonks.com) (more on this in a later blog post).

While we migrated mostly everything without problems we were confronted with the problem that our SSL certificate gave us an error message of the form:

“The certificate for this website was signed by an unknown certifying authority”

This was rather strange because the same certificate worked with Apache just fine. After some time and searching for a solution we found that we had to tell Nginx to use the SSL Chain file as well. The only problem is that Nginx does not have a explicit parameter like Apache has. In Apache the SSL config looks like this (we use a GoDaddy certificate):

SSLEngine On  
SSLCertificateFile /etc/httpd/ssl/youcert.crt  
SSLCertificateKeyFile /etc/httpd/ssl/yourkey.key  
SSLCertificateChainFile /etc/httpd/ssl/gd\_bundle.crt

Now, in order to get this working in Nginx you need to append the “gd\_bundle.crt” to your crt file, which is quite simple with the following commands (do a backup of any files before doing this!):

cat gd\_bundle.crt >> yourcert.crt

Then simply restart Ngnix and all is back to normal (but just really faster with Nginx then with anything else:-) ).