Hello Simone Here some improvement :
*The following is an example configuration, to reduce the CPU load it is recommended to run one worker process only and to enable keep-alive connections:* *worker_processes <http://wiki.nginx.org/NginxHttpCoreModule#worker_processes> 1;*http <http://wiki.nginx.org/NginxHttpCoreModule#http> { server <http://wiki.nginx.org/NginxHttpCoreModule#server> { listen <http://wiki.nginx.org/NginxHttpCoreModule#listen> 443; ssl <http://wiki.nginx.org/NginxHttpSslModule#ssl> on; ssl_certificate <http://wiki.nginx.org/NginxHttpSslModule#ssl_certificate> /usr/local/nginx/conf/cert.pem; ssl_certificate_key <http://wiki.nginx.org/NginxHttpSslModule#ssl_certificate_key> /usr/local/nginx/conf/cert.key;* keepalive_timeout <http://wiki.nginx.org/NginxHttpCoreModule#keepalive_timeout> 70;* }} When using a chain of certificates, just append the extra certificates to your .crt file (cert.pem in the example). The server certificate needs to be the first on the file, otherwise you'll get a mismatch between private and public keys. *Since Nginx version 0.7.14 the preferred way of enabling SSL is by using the `ssl` parameter of the `listen` directive:* server <http://wiki.nginx.org/NginxHttpCoreModule#server> {* listen <http://wiki.nginx.org/NginxHttpCoreModule#listen> 443 default_server ssl <http://wiki.nginx.org/NginxHttpSslModule#ssl>;* ssl_certificate <http://wiki.nginx.org/NginxHttpSslModule#ssl_certificate> /usr/local/nginx/conf/cert.pem; ssl_certificate_key <http://wiki.nginx.org/NginxHttpSslModule#ssl_certificate_key> /usr/local/nginx/conf/cert.key; ...} Ref : http://wiki.nginx.org/HttpSslModule I put the parameter and the reason in bold. You do what you want, I report because they are suggested best practices that I found reading a bit about ssl and Nginx. Richard On Mon, Dec 17, 2012 at 12:37 PM, Richard Vézina < [email protected]> wrote: > I am not sure, the only thing that I know is that Nginx is not showing up > until I stop and restart it. Maybe it was needing a reload as you said at > last... > > Richard > > > On Fri, Dec 14, 2012 at 3:01 PM, Niphlod <[email protected]> wrote: > >> tly with the install and this line is the culprit ? > > > --
