# Speed up adding 1 domain to multi domain cert **URL:** \ **Category:** Help\ **Created:** [January 27, 2017, 6:41pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562 "2017-01-27T18:41:31Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![danielflippance](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danielflippance/32/41_2.png) [@danielflippance](https://community.letsencrypt.org/u/danielflippance)\ **Post date:** [January 27, 2017, 6:41pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562/1 "2017-01-27T18:41:31Z")
I’m investigating using a Let’sEncrypt multi-domain cert where I was previously using a wildcard cert from another provider. What I’m finding is that when I add 1 new domain to the list of valid domains, that the time it takes Let’sEncrypt to re-authenticate all the existing domains is quite long, whereas the part of the time taken for the new domain is only a few seconds. For example, if each domain takes 5 seconds to authenticate: - 1. We have an existing Let’sEncrypt cert for 90 domains which have all been successfully authenticated - 1. We want to add one new domain - 1. Let’sEncrypt re-authenticates all 90 domains plus the new 1 - 1. Time taken is 455 seconds Is there any way to configure the cert request such that only the 1 new domain needs to be authenticated and so the cert request only takes the shorter 5 seconds? ---
**Author:** ![danielflippance](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danielflippance/32/41_2.png) [@danielflippance](https://community.letsencrypt.org/u/danielflippance)\ **Post date:** [January 27, 2017, 7:23pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562/2 "2017-01-27T19:23:53Z")
Seems this may be due to the library I’m using ([https://github.com/dmathieu/sabayon](https://github.com/dmathieu/sabayon)) to request the certificate rather than due to the way Let’s Encrypt works, but I’m not sure. Can anyone comment? ---
**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:** [January 27, 2017, 9:25pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562/3 "2017-01-27T21:25:05Z")
It may depend how recently the previous certificate was issued. The ACME protocol has a concept of authorization (`authz`) which connotes authority to request certificates for a particular name. There is a period of time during which your client could reuse this authorization (whether it does depends on how the client is implemented) instead of obtaining a new one, which could make reissuance with an additional name faster because the DV challenges wouldn’t have to be re-performed for the existing names. ---
**Author:** ![danielflippance](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danielflippance/32/41_2.png) [@danielflippance](https://community.letsencrypt.org/u/danielflippance)\ **Post date:** [January 27, 2017, 10:22pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562/4 "2017-01-27T22:22:33Z")
I see, thanks. Any idea how long that period is? A few hours; a few days? ---
**Author:** ![sigprof](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sigprof/32/19781_2.png) [@sigprof](https://community.letsencrypt.org/u/sigprof)\ **Post date:** [January 27, 2017, 10:30pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562/5 "2017-01-27T22:30:36Z")
Apparently sabayon [registers a new account with a fresh account key for every attempt to issue a certificate](https://github.com/dmathieu/sabayon/blob/master/certs/create.go#L15); this means there is no possibility to reuse existing authorizations (which are tied to the previous account key). This avoids the risk of leaking the account private key (which would allow the attacker to issue certificates for your domains while the authorizations are valid), but slows down the issuance process, as you noticed. Currently authorizations are valid for 60 days, but there were some plans to decrease that time. ---
**Author:** ![danielflippance](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danielflippance/32/41_2.png) [@danielflippance](https://community.letsencrypt.org/u/danielflippance)\ **Post date:** [January 28, 2017, 6:53pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562/6 "2017-01-28T18:53:23Z")
If the issue with registering a new account on every attempt were resolved, how long should I expect it to take to add 1 new domain to an existing cert of 90 domains? Still 455 seconds or would this be shortened? I’m only concerned about the time it takes to add a new domain, rather than how long it takes to renew the certificate every 60 days. ---
**Author:** ![jsha](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jsha/32/12_2.png) [@jsha](https://community.letsencrypt.org/u/jsha)\ **Post date:** [January 28, 2017, 6:59pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562/7 "2017-01-28T18:59:03Z")
In theory, closer to the 5 seconds required to authorize a single new FQDN, assuming that the authorizations for the other FQDNs are still active. Keep in mind that you’ll only be able to do this reissuance about 20 times per week, because of our [Certificates Per Name rate limit](https://letsencrypt.org/docs/rate-limits/). ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [February 27, 2017, 7:12pm UTC](https://community.letsencrypt.org/t/speed-up-adding-1-domain-to-multi-domain-cert/26562/8 "2017-02-27T19:12:10Z")
Closed on February 27, 2017, 7:12pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.