# How to manage and add names to /etc/letsencrypt/live?

**URL:** <https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923>\
**Category:** Help\
**Created:** [July 26, 2017, 12:24pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923 "2017-07-26T12:24:07Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![ppKrauss](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@ppKrauss](https://community.letsencrypt.org/u/ppKrauss)\
**Post date:** [July 26, 2017, 12:24pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/1 "2017-07-26T12:24:07Z")

</div>

I am using the command `certbot --nginx` that generated all certificates… But all with only one and aleatory domain name…

1. Can I change or choose the name? The name is the only file at `/etc/letsencrypt/live`.

2. Ideal to my server is to use 2 or more certificates, one for each domain name (certifing its subdomains), can I do it?   
How to manage names, spliting a big certificate into “one certificate per domain”?

---

<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:** [July 26, 2017, 6:39pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/2 "2017-07-26T18:39:53Z")

</div>

Hi @ppKrauss,

[quote="ppKrauss, post:1, topic:38923"]  
Can I change or choose the name? The name is the only file at /etc/letsencrypt/live.  
Ideal to my server is to use 2 or more certificates, one for each domain name (certifing its subdomains), can I do it? [/quote]

Yes, when first creating the certificate you can use `--cert-name` to specify which name will be used in `/etc/letsencrypt` to refer to that certificate.

> [@](#):
>
> How to manage names, spliting a big certificate into "one certificate per domain"?

Certbot obtains one new certificate each time you run it. So the idea would be to run Certbot one time per domain, if that's what you want, like

`certbot certonly --nginx -d www.onedomain.com -d onedomain.com certbot certonly --nginx -d www.anotherdomain.com -d anotherdomain.com certbot certonly --nginx -d www.thirddomain.com -d thirddomain.com`

If the names that you obtain certificates for are _subdomains_ of the same domain, you might run into a rate limit (Certificates Per Registered Domain) by doing this.

> **[Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/)**
>
> Let’s Encrypt provides rate limits to ensure fair usage by as many people as possible. We believe these rate limits are high enough to work for most people by default. We’ve also designed them so renewing a certificate almost never hits a...

If they are independent domains, this shouldn't be a problem at all.

---

<div class="post-metadata">

**Author:** ![ppKrauss](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@ppKrauss](https://community.letsencrypt.org/u/ppKrauss)\
**Post date:** [July 26, 2017, 11:28pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/3 "2017-07-26T23:28:59Z")

</div>

Thanks @schoen. About automation with `certbot --nginx` that read (parse) all and show to me, to decide what to do … It is a **interactive mode**. With the use of `-d` we lost lists and the interactive mode… How to preserve interactive mode?

EDIT: hum… here, the name is “autodiscovery”… I see but can’t test in production… "`--installer` that will help in domain names autodiscovery`"

---

<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:** [July 26, 2017, 11:30pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/4 "2017-07-26T23:30:14Z")

</div>

Well, you can either choose the names from the menu or specify them on the command line. We don’t really have anything in between the two cases. If you don’t specify `-d`, you can still choose to include or exclude particular names interactively.

---

<div class="post-metadata">

**Author:** ![ppKrauss](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@ppKrauss](https://community.letsencrypt.org/u/ppKrauss)\
**Post date:** [August 12, 2017, 2:56am UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/5 "2017-08-12T02:56:46Z")

</div>

Hi, only checking, seems a **bug**. When do this sequence of steps,

1. use `certbot --nginx` with (autodiscovery and) success… Generates a certificate for all domains: for `MyName` and `MyName2`.
2. run `certbot --nginx --cert-name MyName` generates error. See dump below.
3. run `certbot --nginx`… Same error. The sequence was destroied something that not was my intention, and is not evident for _undo_.

The error:

```
Error while running nginx -c /etc/nginx/nginx.conf -t.

nginx: [emerg] a duplicate listen 0.0.0.0:80 in /etc/nginx/sites-enabled/MyName2:12
nginx: configuration file /etc/nginx/nginx.conf test failed

The nginx plugin is not working; there may be problems with your existing configuration.
The error was: MisconfigurationError('Error while running nginx -c /etc/nginx/nginx.conf -t.\n\nnginx: [emerg] a duplicate listen 0.0.0.0:80 in /etc/nginx/sites-enabled/MyName2:12\nnginx: configuration file /etc/nginx/nginx.conf test failed\n',)
```

---

<div class="post-metadata">

**Author:** ![ppKrauss](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@ppKrauss](https://community.letsencrypt.org/u/ppKrauss)\
**Post date:** [August 12, 2017, 3:07am UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/6 "2017-08-12T03:07:17Z")

</div>

Another bug: running `certbot --nginx --cert-name domain2` not changes the list of domains, no filter for domain2, so **no way to organize and group** my certificates in two sets, one for `--cert-name Domain1` other for `--cert-name Domain2`.

---

<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:** [August 12, 2017, 5:23pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/7 "2017-08-12T17:23:36Z")

</div>

What version of Certbot are you using? I want to ask the developer who implemented this functionality, but I want to know if it could be a bug that’s been fixed in the meantime.

---

<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:** [August 12, 2017, 5:24pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/8 "2017-08-12T17:24:18Z")

</div>

> [@ppKrauss](#):
>
> Another bug: running certbot --nginx --cert-name domain2 not changes the list of domains, no filter for domain2, so no way to organize and group my certificates in two sets, one for --cert-name Domain1 other for --cert-name Domain2.

I didn't understand what you meant here. Could you describe this problem another way (or else in Portuguese)?

---

<div class="post-metadata">

**Author:** ![ppKrauss](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@ppKrauss](https://community.letsencrypt.org/u/ppKrauss)\
**Post date:** [August 13, 2017, 11:08pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/9 "2017-08-13T23:08:04Z")

</div>

Hi @schoen, I am using _certbot v0.14.2_, at UBUNTU 16 LTS with _Nginx v1.10.3_… About first and second bug, was a [non-reversible](https://en.wikipedia.org/wiki/Reversible_computing) phenomenon 😉

The problem, that I see as bug, is “how to back to the initial state?”. As workaround I used backup files of `/etc/nginx/sites-available/` and my `snippets/ssl-*.conf` adapting to the changes of certbot.

---

<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:** [August 14, 2017, 4:55pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/10 "2017-08-14T16:55:12Z")

</div>

> [@ppKrauss](#):
>
> The problem, that I see as bug, is “how to back to the initial state?”. As workaround I used backup files of /etc/nginx/sites-available/ and my snippets/ssl-\*.conf adapting to the changes of certbot.

There's an old little-used feature called `certbot rollback` which is meant for this situation. It should restore your server configuration that was modified by Certbot. You can also indicate the number of checkpoints to roll back with `--checkpoints` (the default is 1).

---

<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:** [September 13, 2017, 4:55pm UTC](https://community.letsencrypt.org/t/how-to-manage-and-add-names-to-etc-letsencrypt-live/38923/11 "2017-09-13T16:55:19Z")

</div>

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