# Adding more sites

**URL:** <https://community.letsencrypt.org/t/adding-more-sites/14788>\
**Category:** Uncategorized\
**Created:** [April 22, 2016, 11:51pm UTC](https://community.letsencrypt.org/t/adding-more-sites/14788 "2016-04-22T23:51:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![square\_eyes](https://avatars.discourse-cdn.com/v4/letter/s/3bc359/32.png) [@square\_eyes](https://community.letsencrypt.org/u/square_eyes)\
**Post date:** [April 22, 2016, 11:51pm UTC](https://community.letsencrypt.org/t/adding-more-sites/14788/1 "2016-04-22T23:51:10Z")

</div>

Hi hopefully this hasn’t been asked before (I did a search).

I successfully issued and installed a cert on my windows Xampp install for one site. I now want to secure another site I have on the same machine.

Do I issue a cert per site, or reissue my existing cert, adding my original site, plus the new one I want included in the cert?

Or can I just use the cert that’s there?

---

<div class="post-metadata">

**Author:** ![SilverbackNet](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/silverbacknet/32/1032_2.png) [@SilverbackNet](https://community.letsencrypt.org/u/SilverbackNet)\
**Post date:** [April 23, 2016, 1:52am UTC](https://community.letsencrypt.org/t/adding-more-sites/14788/2 "2016-04-23T01:52:05Z")

</div>

You reissue adding the new site:  
`./letsencrypt-auto certonly --webroot -w /var/www/example -d www.example.com -d example.com -w /var/www/support -d support.example.com`

LE will ask if you want to expand the certificate or cancel. When you expand, it’ll reissue with all requested domains (as long as it can reach them all).

---

<div class="post-metadata">

**Author:** ![square\_eyes](https://avatars.discourse-cdn.com/v4/letter/s/3bc359/32.png) [@square\_eyes](https://community.letsencrypt.org/u/square_eyes)\
**Post date:** [April 23, 2016, 4:47am UTC](https://community.letsencrypt.org/t/adding-more-sites/14788/3 "2016-04-23T04:47:29Z")

</div>

great thanks:) Do I need separate entries for subdomains?

---

<div class="post-metadata">

**Author:** ![SilverbackNet](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/silverbacknet/32/1032_2.png) [@SilverbackNet](https://community.letsencrypt.org/u/SilverbackNet)\
**Post date:** [April 23, 2016, 6:59am UTC](https://community.letsencrypt.org/t/adding-more-sites/14788/4 "2016-04-23T06:59:03Z")

</div>

Yep, all domains and subdomains the cert will cover have to be included. LE doesn’t allow wildcard certs, which are the only way to cover all subs of a domain without individually naming them.

btw, I just found out about the `--expand --agree-tos -q` options, which will make my quick server setup even faster. Add them to the command above and it just runs without any prompts.

---

<div class="post-metadata">

**Author:** ![square\_eyes](https://avatars.discourse-cdn.com/v4/letter/s/3bc359/32.png) [@square\_eyes](https://community.letsencrypt.org/u/square_eyes)\
**Post date:** [April 23, 2016, 7:02am UTC](https://community.letsencrypt.org/t/adding-more-sites/14788/5 "2016-04-23T07:02:52Z")

</div>

Thanks again. All up and running:)

---

<div class="post-metadata">

**Author:** ![Biker](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/biker/32/49_2.png) [@Biker](https://community.letsencrypt.org/u/Biker)\
**Post date:** [April 25, 2016, 7:51am UTC](https://community.letsencrypt.org/t/adding-more-sites/14788/6 "2016-04-25T07:51:22Z")

</div>

> [@SilverbackNet](#):
>
> btw, I just found out about the --expand --agree-tos -q options, which will make my quick server setup even faster. Add them to the command above and it just runs without any prompts.

I have comfortably entered such options in the `/etc/letsencrypt/cli.ini` configuration file. Saves me a lot of typing (and thinking 😄) for options I consider permanent in my setup.

See [User Guide The Let’s Encrypt project — letsencrypt latest documentation](http://letsencrypt.readthedocs.org/en/latest/using.html#configuration-file) for details.