# WildCard Error certbot

**URL:** <https://community.letsencrypt.org/t/wildcard-error-certbot/134647>\
**Category:** Help\
**Created:** [September 27, 2020, 11:03am UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647 "2020-09-27T11:03:40Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![lmery](https://avatars.discourse-cdn.com/v4/letter/l/e56c9b/32.png) [@lmery](https://community.letsencrypt.org/u/lmery)\
**Post date:** [September 27, 2020, 11:03am UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647/1 "2020-09-27T11:03:40Z")

</div>

Hello

I am trying to renew my wildcard certificate on the delegated zone \* .sio.lyceefulbert.fr

I use the command

certbot -d \* .sio.lyceefulbert.fr --manual --preferred-challenges dns certonly

but certbot tries to generate me a certificate for one of my aliases namely my gitlab server.

dns-01 challenge for [gitlab.sio.lyceefulbert.fr](http://gitlab.sio.lyceefulbert.fr)

My order worked perfectly before, but I forgot an option to clarify that it is a wildard.

cordially

My domain is:sio.lyceefulbert.fr

I ran this command:certbot -d \*.sio.lyceefulbert.fr --manual --preferred-challenges dns certonly

It produced this output:dns-01 challenge for [gitlab.sio.lyceefulbert.fr](http://gitlab.sio.lyceefulbert.fr)

My web server is (include version): Nginx

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

---

<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:** [September 27, 2020, 11:24am UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647/2 "2020-09-27T11:24:55Z")

</div>

The only way I see that happening is if:

- you had a file or directory named `gitlab.sio.lyceefulbert.fr` in your working directory, and
- you didn't put quotes around `*.sio.lyceefulbert.fr`

So maybe try:

```
certbot -d "*.sio.lyceefulbert.fr" --manual --preferred-challenges dns certonly

```

Otherwise, could you please post the contents of `/var/log/letsencrypt/letsencrypt.log`?

---

<div class="post-metadata">

**Author:** ![lmery](https://avatars.discourse-cdn.com/v4/letter/l/e56c9b/32.png) [@lmery](https://community.letsencrypt.org/u/lmery)\
**Post date:** [September 27, 2020, 12:59pm UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647/3 "2020-09-27T12:59:37Z")

</div>

Hello

Thank you very much, that fixed the problem.

I was doing this command without the quotes until now and it had never been a problem.

Thank you very much for your quick response

Best regards

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [September 27, 2020, 1:32pm UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647/4 "2020-09-27T13:32:06Z")

</div>

> [@lmery](#):
>
> I was doing this command without the quotes until now and it had never been a problem.

That's because one almost never runs certbot in a directory where Bash can expand the wildcard. So when one actually _does_ walk into ~~Mordor~~ such a directory, one doesn't expect Bash to expand the wildcard and you'll run into this issue.

Note: this is a Bash thing, not a certbot thing 🙂

---

<div class="post-metadata">

**Author:** ![lmery](https://avatars.discourse-cdn.com/v4/letter/l/e56c9b/32.png) [@lmery](https://community.letsencrypt.org/u/lmery)\
**Post date:** [September 27, 2020, 2:45pm UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647/5 "2020-09-27T14:45:17Z")

</div>

Indeed I should not have made the command in a user directory .... Well done and thank you again. 🙂

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [September 28, 2020, 2:29am UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647/6 "2020-09-28T02:29:00Z")

</div>

> [@Osiris](#):
>
> So when one actually _does_ walk into ~~Mordor~~ such a directory, one doesn't expect Bash to expand the wildcard and you'll run into this issue.

What a great way of putting it!

![4gi9g8](https://global.discourse-cdn.com/letsencrypt/original/3X/1/c/1cd4bc611ae3e31dbab17c1466bec45e1bd18bbd.jpeg)

😀

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [September 28, 2020, 3:56am UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647/7 "2020-09-28T03:56:00Z")

</div>

That's fantastic. 🤣

And here I am out of likes for awhile. ❤

This one goes into the handbook fo' sho'.

---

<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:** [October 28, 2020, 3:56am UTC](https://community.letsencrypt.org/t/wildcard-error-certbot/134647/8 "2020-10-28T03:56:14Z")

</div>

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