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: *.successbuilder.com
I ran this command:
It produced this output:
My web server is (include version): Windows Server 2016 Standard 64-bit
The operating system my web server runs on is (include version): IIS - (Internet information service - 10.0.14393.0)
My hosting provider, if applicable, is: Liquid Web Data Center
I can login to a root shell on my machine (yes or no, or I don’t know): no
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): We are using RDP to access all or websites
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
You need to choose one of the client applications from the page that @JuergenAuer linked to. I’m not very familiar with the situation on Windows, so I don’t think I can help you much with that choice.
Note that wildcards are more complex to deal with than non-wildcards. By Let’s Encrypt policy, wildcard certificates can only be obtained when you prove your control over your domain by making requested DNS TXT records. This is described in
However, this process would have to be repeated by creating new DNS TXT records every time the certificate has to be renewed. If you don’t have a suitable form of integration between your web server and your DNS server, it won’t be possible to automate this process, and then the renewal process will be much more time-consuming.