# Wildcard Certificate error

**URL:** <https://community.letsencrypt.org/t/wildcard-certificate-error/97468>\
**Category:** Help\
**Created:** [July 9, 2019, 5:41am UTC](https://community.letsencrypt.org/t/wildcard-certificate-error/97468 "2019-07-09T05:41:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ahaloans](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@Ahaloans](https://community.letsencrypt.org/u/Ahaloans)\
**Post date:** [July 9, 2019, 5:41am UTC](https://community.letsencrypt.org/t/wildcard-certificate-error/97468/1 "2019-07-09T05:41:51Z")

</div>

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](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: [aadrila.com](http://aadrila.com)

I ran this command: sudo ./certbot-auto --authenticator standalone --installer apache --debug -v --server [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory) certonly -d \*.[aadrila.com](http://aadrila.com/)

It produced this output: Performing the following challenges:  
Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. You may need to use an authenticator plugin that can do challenges over DNS.  
Exiting abnormally:  
Traceback (most recent call last):  
File “/opt/[eff.org/certbot/venv/bin/letsencrypt](http://eff.org/certbot/venv/bin/letsencrypt)”, line 11, in   
sys.exit(main())  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/main.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/main.py)”, line 1379, in main  
return config.func(config, plugins)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/main.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/main.py)”, line 1262, in certonly  
lineage = \_get\_and\_save\_cert(le\_client, config, domains, certname, lineage)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/main.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/main.py)”, line 120, in \_get\_and\_save\_cert  
lineage = le\_client.obtain\_and\_enroll\_certificate(domains, certname)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/client.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/client.py)”, line 406, in obtain\_and\_enroll\_certificate  
cert, chain, key, \_ = self.obtain\_certificate(domains)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/client.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/client.py)”, line 349, in obtain\_certificate  
orderr = self.\_get\_order\_and\_authorizations(csr.data, self.config.allow\_subset\_of\_names)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/client.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/client.py)”, line 385, in \_get\_order\_and\_authorizations  
authzr = self.auth\_handler.handle\_authorizations(orderr, best\_effort)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth\_handler.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth_handler.py)”, line 61, in handle\_authorizations  
achalls = self.\_choose\_challenges(authzrs)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth\_handler.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth_handler.py)”, line 181, in \_choose\_challenges  
combinations)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth\_handler.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth_handler.py)”, line 297, in gen\_challenge\_path  
return \_find\_smart\_path(challbs, preferences, combinations)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth\_handler.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth_handler.py)”, line 333, in \_find\_smart\_path  
\_report\_no\_chall\_path(challbs)  
File “/opt/[eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth\_handler.py](http://eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/auth_handler.py)”, line 372, in \_report\_no\_chall\_path  
raise errors.AuthorizationError(msg)  
AuthorizationError: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. You may need to use an authenticator plugin that can do challenges over DNS.  
Please see the logfiles in /var/log/letsencrypt for more details.

My web server is (include version): Apache2.0

The operating system my web server runs on is (include version): Linux

My hosting provider, if applicable, is: AWS

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): Certbot

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [July 9, 2019, 5:53am UTC](https://community.letsencrypt.org/t/wildcard-certificate-error/97468/2 "2019-07-09T05:53:07Z")

</div>

> [@Ahaloans](#):
>
> You may need to use an authenticator plugin that can do challenges over DNS.

This part of the error message explains what is happening.

With Certbot, you would need to use [Welcome to certbot-dns-route53’s documentation! — certbot-dns-route53 0 documentation](https://certbot-dns-route53.readthedocs.io/en/latest/) to generate your wildcard certificate.

However, it is not available when using certbot-auto. So your options are to install Certbot and the DNS plugin from your operating system's repositories (if available), or choose another ACME client, like acme.sh, which [can also issue wildcards using Route53](https://github.com/Neilpang/acme.sh/wiki/dnsapi#10-use-amazon-route53-domain-api).

Since you are using Amazon AMI, I don't think that the Certbot Route53 plugin is available for your OS.

---

<div class="post-metadata">

**Author:** ![Ahaloans](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@Ahaloans](https://community.letsencrypt.org/u/Ahaloans)\
**Post date:** [July 9, 2019, 5:56am UTC](https://community.letsencrypt.org/t/wildcard-certificate-error/97468/3 "2019-07-09T05:56:14Z")

</div>

Then what could be a solution if I am using Amazon Linux AMI.

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [July 9, 2019, 5:59am UTC](https://community.letsencrypt.org/t/wildcard-certificate-error/97468/4 "2019-07-09T05:59:06Z")

</div>

You can try [acme.sh](https://github.com/Neilpang/acme.sh). As I mentioned, it also supports wildcards using Route53: [https://github.com/Neilpang/acme.sh/wiki/dnsapi#10-use-amazon-route53-domain-api](https://github.com/Neilpang/acme.sh/wiki/dnsapi#10-use-amazon-route53-domain-api)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [August 8, 2019, 6:09am UTC](https://community.letsencrypt.org/t/wildcard-certificate-error/97468/5 "2019-08-08T06:09:02Z")

</div>

Closed on August 8, 2019, 6:09am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.