NGINX - performance HTTP server Support Forums

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Unofficial (YET) support forums for NGINX, a performance HTTP server.

Pages: [1]   Go Down

Author Topic: SSL Chain problem  (Read 490 times)

0 Members and 1 Guest are viewing this topic.

andy33gmail

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 1
    • View Profile
SSL Chain problem
« on: September 23, 2009, 08:17:53 PM »
Hi Guys,

I'm using nginx as a reverse proxy for a local site, to allow https access. The site is https://members.sealsswimming.co.uk , it is a reverse proxy to http://members.sealsswimming.co.uk . Bear in mind this is a live site for a real company (but no-one's been informed about / linked to the https port). To view pages without the silly "mixed content" warnings, you can use https://members.sealsswimming.co.uk/noimages.html

It uses a certificate bought from 123-reg, provided by Alpha SSL.

I've tried setting up the certificates as per these instructions: http://www.digicert.com/ssl-certificate-installation-nginx.htm , using the certificate from here http://www.alphassl.com/support/install-root-certificate.html - which I've appended to my own key.

The server "works" and does not make any errors to the terminal or the log file.

However, on some machines, Firefox is whinging about the site not being trusted, and some SSL checkers are having problems:
-http://www.sslshopper.com/ssl-checker.html
-http://www.codefromthe70s.org/certcheck.aspx?t=members.sealsswimming.co.uk
interestingly, this one is ok:
http://www.digicert.com/help/

Does anyone have a clue why this isn't working?

Andy
Logged

chrisfarms

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 1
  • Just started
    • View Profile
Re: SSL Chain problem
« Reply #1 on: March 04, 2010, 12:59:24 PM »
I know this thread is dead, but it is ranking very high on google:

Quote
if you have a chain certificate file (sometimes called an intermediate certificate) you don't specify it separately like you do in Apache. Instead you need to add the information from the chain cert to the end of your main certificate file. This can be done by typing "cat chain.crt >> mysite.com.crt" on the command line. Once that is done you won't use the chain cert file for anything else, you just point Nginx to the main certificate file.

also:

Quote
when using chain certificates, just append the extra certificates into your .crt file (cert.pem in the example). Your own certificate needs to be on top of the file, otherwise key get a mismatch with the key.

http://wiki.nginx.org/NginxHttpSslModule
Logged
Pages: [1]   Go Up
« previous next »
 

Page created in 0.033 seconds with 20 queries.