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:
I ran this command:
It produced this output:
it tried to DNS validate the domain names separately and failed
My web server is (include version):
The operating system my web server runs on is (include version):
Windows Server 2016
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot): WACS version 220.127.116.118 (release, pluggable, standalone, 64-bit)
My site normally uses a wildcard certificate *.chargerback.net. I have successfully used WACS to generate/auto install for the last 10 renewals. However, I have had to add bindings for two additional domain names, that I don't need LetsEncrypt certificates for. But when I try to run WACS to generate the certificate, it asks me about the bindings, then tries to create a separate certificate for each one. This fails because (I assume) the subdomains of chargerback.net are CNAMEs. Is there any way to get WACS to generate a wildcard certificate and bind to the correct subdomains?