I have a CentOS 7 test server with a functional Let’s Encrypt certificate (let’s call it myserver.net). I have installed a demo of my app at www.myserver.net/index.php. A potential customer wants to try it out. I would like to add a new domain & certificate to this server : mycustomer.net. Right now I don’t think I need to set up a virtual host because there is only one app installed there, with myserver.net and mycustomer.net pointing at the same index.php
Is that correct ? I get an error message but I think there is an open bug report on github and they are currently trying to solve it : Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA
Is there something to do about it right now or I should I wait ?
Another question, what if I only create a subdomain : mycustomer.myserver.net ? Right now I get a certificate error with Chrome. Is there an easy way to use myserver.net certificate on all its subdomains ?
I don't know if new packages are available for CentOS yet. If you want to upgrade, you may have to use certbot-auto or another installation method, which comes with its own inconveniences.
You would have to issue a new certificate, with a Certbot command similar to what was used to create the certificate originally. For example, maybe:
At the moment, there isn't really another option available. However, Let's Encrypt plans to start offering wildcard certificates February 27. You would have to upgrade Certbot, and use DNS-01 validation, but you could then get a certificate for *.myserver.net.