It produced this output:
I got success but a number of new subdomains that I have setup don’t appear to be getting added to the cert. I feel like I am capped or limited somehow… In truth, the initial certbot --nginx commands are straight forward, I am certain that I don’t fully understand how to augment my certs properly. Thank you for any help you can offer and what a great product/service you have.
My web server is (include version): nginx 1.14
The operating system my web server runs on is (include version): ubuntu 18
My hosting provider, if applicable, is: AWS/EC2
I can login to a root shell on my machine (yes or no, or I don’t know): YES
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): NO
If you have a lot of subdomains, you have two options:
creating one certificate with all subdomains. You can add max. 100 domain names in one certificate. So 20 << 100, you can add a lot of new subdomains. But then you need (if you use the -d option) always a list of all subdomains. That's complicated.
creating one certificate per subdomain. You can create max. 50 new certificates per domain per week. Then you need one vHost per subdomain
Checking your list - there are new subdomains, but not 50 in one week. Currently, 20 subdomains.
So creating one certificate per subdomain should work without hitting a limit.
Both versions (one certificate with all subdomains or one certificate per subdomain) are possible.
Thank you for your input. The major setback at this moment is every client/partner wants me to know, learn and master a dozen different technologies. I must add letsencrypt to that list … my real issue is time. Thanks so much for all of your help. I think I am slowly arriving at an approach that will allow me to manage all of the subdomains …