# Websites now on two servers

**URL:** <https://community.letsencrypt.org/t/websites-now-on-two-servers/63264>\
**Category:** Help\
**Created:** [May 31, 2018, 12:16am UTC](https://community.letsencrypt.org/t/websites-now-on-two-servers/63264 "2018-05-31T00:16:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![doconnor](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/doconnor/32/23683_2.png) [@doconnor](https://community.letsencrypt.org/u/doconnor)\
**Post date:** [May 31, 2018, 12:16am UTC](https://community.letsencrypt.org/t/websites-now-on-two-servers/63264/1 "2018-05-31T00:16:06Z")

</div>

I have two websites [https://www.transsee.ca/](https://www.transsee.ca/) and [https://doconnor.transsee.ca/](https://doconnor.transsee.ca/) with different content.

Originally they where two vhosts on the same apache server and I set up their encryption together.

I have now moved [https://www.transsee.ca/](https://www.transsee.ca/) to a different server (different IP, different physical location). When I do a dry-run with certbot to renew [https://www.transsee.ca/](https://www.transsee.ca/) it says it fails because of a problem with [https://doconnor.transsee.ca](https://doconnor.transsee.ca)

It’s not clear the best way for me to renew both these web sites.

---

<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:** [May 31, 2018, 12:53am UTC](https://community.letsencrypt.org/t/websites-now-on-two-servers/63264/2 "2018-05-31T00:53:26Z")

</div>

Hi @doconnor,

One option which might not be the safest is the Certbot `--allow-subset-of-names` option (which treats the renewal as successful even when not all names can be renewed).

A more correct option is to specify the particular names that you want to be included in the cert, as well as the cert name. If the cert name from `certbot certificates` is `www.transsee.ca` then on that server you could run

`certbot certonly --force-renew --cert-name www.transsee.ca -d www.transsee.ca -d transsee.ca`

And on the other server you could run

`certbot certonly --force-renew --cert-name www.transsee.ca -d doconnor.transsee.ca`

The one thing that might be confusing as a result on the second server is that the cert name would be unchanged, so the cert on the second server would be named after a hostname that wasn’t actually covered by the cert.

---

<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:** [June 30, 2018, 12:53am UTC](https://community.letsencrypt.org/t/websites-now-on-two-servers/63264/3 "2018-06-30T00:53:29Z")

</div>

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