SSL How to enable https for my domain

Hi

I was just install latest beta 09 centminmod (spdy=n - https=y) and i don't remember what i must edit now to enable https for my domain using the included https self signed certificate that Centminmod Nginx vhost create for me.....

---

 

When i use :

Code:

https://mydomain.com

I am getting this:

Code:

This webpage is not available
DNS_PROBE_FINISHED_NXDOMAIN

Normal http is working fine but not the https....


This one is for SPDY and not for https2 (are they need exact same steps to work? ) :

Nginx SPDY SSL Configuration - CentminMod.com LEMP Nginx web stack for CentOS

Maybe do i have to enable the temp redirect 30 to config file?

As i didn't edit anything at all as i did a clean install and just create the vhost....

 

That flush dns did the trick and is working now

As i want to use now only https for the domain how can i forward all http requests to:

Code:

https://mydomain.com

?
Thanks

 

Ok one last one

If i want to get a redirect from www to none?

for example:

Code:

http://mydomain.com
http://www.mydomain.com
https://www.mydomain.com

All the above to redirect to :

Code:

https://mydomain.com

This is what i have there:

Code:

#server {
#            listen   80;
#            server_name mydomain.com;
#            return 301 $scheme://www.mydomain.com$request_uri;
#       }

server {
  server_name mydomain.com www.mydomain.com;

 

Please confirm that you mean to uncomment the code like this and keep both server { ? :

Code:

server {
  listen  80;
  server_name mydomain.com www.mydomain.com;
  return 302 https://mydomain.com$request_uri;
  }

server {
  server_name mydomain.com www.mydomain.com;

or do you mean to do this?

Code:

#server {
# listen  80;
# server_name mydomain.com www.mydomain.com;
# return 302 https://mydomain.com$request_uri;
# }

server {
  listen  80;
  server_name mydomain.com www.mydomain.com;
  return 302 https://mydomain.com$request_uri;

 

Ok tested and working great

Now one last step to replace the self signed certificate with a valid comodo one

But i will try it in the next 1-2 days so you can get rest with my questions

Do we have any tutorial for this as we need to replace the tutorial for SPDY with the new https2 ?

 

Ok i just get a comodo ssl trial for 90 days from gogetssl

I use SHA2 256Bit.

I upload the files here:

Code:

/usr/local/nginx/conf/ssl/mydomain.com

and is working

But i have some questions :

Nginx is looking for file:

Code:

/usr/local/nginx/conf/ssl/mydomain.com/dhparam.pem

Is this a must? And what if i have a vhost without auto ssl creation and the file is missing? Can i create it? How?

Also is this line needed for http2 in mydomain.com.ssl.conf?

Code:

add_header Alternate-Protocol  443:npn-spdy/3;

Are those settings the same for spdy and http2 or i must adjust them?

Code:

  ssl_ciphers ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA:!CAMELLIA;
  ssl_prefer_server_ciphers   on;
  add_header Alternate-Protocol  443:npn-spdy/3;
  # HTTP Public Key Pinning Header uncomment only one that applies include or exclude domains.
  # You'd want to include subdomains if you're using SSL wildcard certificates
  # include subdomain
  #add_header Public-Key-Pins 'pin-sha256="WO9bFFPwpLuAGtOfotF0KpHYpDwuRgQayUm8mOtk7RE="; pin-sha256="ok8rqdmrPf/KkuNtj+If20Qlw5wW4sDAxHr2dLe59NM="; max-age=604800; includeSubDomains';
  # exclude subdomains
  #add_header Public-Key-Pins 'pin-sha256="WO9bFFPwpLuAGtOfotF0KpHYpDwuRgQayUm8mOtk7RE="; pin-sha256="ok8rqdmrPf/KkuNtj+If20Qlw5wW4sDAxHr2dLe59NM="; max-age=604800';
  #add_header Strict-Transport-Security "max-age=31536000; includeSubdomains;";
  #add_header  X-Content-Type-Options "nosniff";
  #add_header X-Frame-Options DENY;
  #spdy_headers_comp 5;
  ssl_buffer_size 1400;
  ssl_session_tickets on;

I am not sure if it is a configuration error or something else but i can't confirm the http2 here:

Code:

https://www.h2check.org/

but is working...

 

Yes but you can do all steps to get https if you have a previous created vhost without https support except this file....
Or is a solution that i miss if i have already a vhost created without https support to recreate it without any data loss?

 

Ok great

Which is the easiest way if i have a vhost created without https support to add https support without any data loss as if i try to add a new vhost again with the same domain name i will get some issues if i am not wrong.....