# Changed my mind

**URL:** <https://community.letsencrypt.org/t/changed-my-mind/16442>\
**Category:** Uncategorized\
**Created:** [June 1, 2016, 2:38am UTC](https://community.letsencrypt.org/t/changed-my-mind/16442 "2016-06-01T02:38:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![trekkie.forever](https://avatars.discourse-cdn.com/v4/letter/t/ba8739/32.png) [@trekkie.forever](https://community.letsencrypt.org/u/trekkie.forever)\
**Post date:** [June 1, 2016, 2:38am UTC](https://community.letsencrypt.org/t/changed-my-mind/16442/1 "2016-06-01T02:38:51Z")

</div>

Hi,

I created a certificate for my domain @ domain dot com but now I want a SAN certificate to cover www dot domain dot com as well.

What are my options?

I am thinking that I can do  
a) Request a 2nd certificate for www dot domain dot com  
b) Revoke my current certificate and be issued a new SAN certificate covering domain dot com and www dot domain dot com

Suggestions are welcome

Thanks.

---

<div class="post-metadata">

**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\
**Post date:** [June 1, 2016, 4:21am UTC](https://community.letsencrypt.org/t/changed-my-mind/16442/2 "2016-06-01T04:21:46Z")

</div>

Revocation isn’t needed here. That’s something you’d do if your private key is compromised.

Your best option is to re-use the command you used to get the certificate originally, and add another `-d` flag with the additional domain, plus `--expand` in order to tell the client to replace the existing certificate. That will give you a SAN certificate covering both domains.

---

<div class="post-metadata">

**Author:** ![trekkie.forever](https://avatars.discourse-cdn.com/v4/letter/t/ba8739/32.png) [@trekkie.forever](https://community.letsencrypt.org/u/trekkie.forever)\
**Post date:** [June 1, 2016, 10:10am UTC](https://community.letsencrypt.org/t/changed-my-mind/16442/3 "2016-06-01T10:10:54Z")

</div>

Thanks for the info @pfg. I did not use the certbot client but the gethttpsforfree website instead. Is there any option to do this without the official client?

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [June 1, 2016, 11:00am UTC](https://community.letsencrypt.org/t/changed-my-mind/16442/4 "2016-06-01T11:00:18Z")

</div>

> [@trekkie.forever](#):
>
> I did not use the certbot client but the gethttpsforfree website instead. Is there any option to do this without the official client?

Certbot is the official client. It depends if you have root access to use that though.

Using the gethttpsforfree website you'd need to just obtain another certificate.

Alternatively there are various [alternate clients](https://github.com/certbot/certbot/wiki/Links) which might enable you to automate things more effectively than the manual method via gethttpsforfree.

---

<div class="post-metadata">

**Author:** ![trekkie.forever](https://avatars.discourse-cdn.com/v4/letter/t/ba8739/32.png) [@trekkie.forever](https://community.letsencrypt.org/u/trekkie.forever)\
**Post date:** [June 2, 2016, 12:53am UTC](https://community.letsencrypt.org/t/changed-my-mind/16442/5 "2016-06-02T00:53:23Z")

</div>

Thanks for the info, will investigate alternate clients for options similar to “expand” in the official client.