One of the registered domains that i am looking into, currently has a wildcard certificate - with almost ~20 subdomains registered under it. And these subdomain-servers are running independently in multiple instances.
Thus, currently, renewing the certificates becomes a manual process.
I was considering using certbot to automatically configure it (apache and nginx) so that the certificates are renewed automatically.
I went through the document for the rate-limit https://letsencrypt.org/docs/rate-limits/ too.
I just wanted some confirmation on a few things
- Is there any advantage of sticking with a wildcard cert?
- Since there is already a wildcard certificate in place, if i generate certs for the subdomain/servers again (using eg, certbot --niginx), will that add on to the rate limit (if added on the same week)?
- If i have 6 subdomains served by nginx, and i run “certbot --nginx”, and i select all domains. Will this count as 6 separate certificates or just 1 certificate?
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: greenstory.ca
I ran this command: not-yet
It produced this output: not-yet
My web server is (include version): nginx, apache-bitnami
The operating system my web server runs on is (include version): ubuntu
My hosting provider, if applicable, is:
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
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot): 0.31.0