I created a cert I don't need


#1

Hi

I was following the following guide: https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04

I only got a cert for example.com, but I’m having some trouble redirecting my nginx from www to non-www. So I thought, maybe I need a cert for www.example.com. So I created one. But I don’t think I really it, it didn’t solve my problem. So should I delete or change anything in my system for this cert?


#2

Nope. Its fine to let it expire naturally.


#3

Thank you!

I donated to the project the other day as I thought it was great! :smile:

On a similar note. Would I need a cert for the www version in order to redirect from www -> non-www. My nginx currently redirects from http -> https fine. But I am struggling to get it to redirect from www -> non-www. I keep getting a privacy warning net::err_common_name_invalid. My nginx seems ok, I’ve asked on a few places, so I’m left thinking if this is the reason based on this: http://serverfault.com/questions/358616/nginx-https-www-redirect-to-non-www?noredirect=1&lq=1


#4

Thank you! We all appreciate your support!

Yup! Typically you would issue one certificate with both the “www” and the “non-www” domains included. The certificate needs to be valid for both names in order to do the redirects.


#5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.