# Migrating WordPress with HTTPs Secured by LetsEncrypt to New Server

**URL:** <https://community.letsencrypt.org/t/migrating-wordpress-with-https-secured-by-letsencrypt-to-new-server/31186>\
**Category:** Server\
**Created:** [April 2, 2017, 2:15pm UTC](https://community.letsencrypt.org/t/migrating-wordpress-with-https-secured-by-letsencrypt-to-new-server/31186 "2017-04-02T14:15:54Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![jmorahan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jmorahan/32/1873_2.png) [@jmorahan](https://community.letsencrypt.org/u/jmorahan)\
**Post date:** [April 3, 2017, 11:01pm UTC](https://community.letsencrypt.org/t/migrating-wordpress-with-https-secured-by-letsencrypt-to-new-server/31186/14 "2017-04-03T23:01:57Z")

</div>

That’s odd; the command you posted above, `sudo letsencrypt certonly -a webroot --webroot-path=/var/www/html -d mydomain.net -d www.mydomain.net -d forum.mydomain.net -d test.mydomain.net`, would have attempted to obtain such a certificate. Are you sure it succeeded?

---

_[View the full topic](https://community.letsencrypt.org/t/migrating-wordpress-with-https-secured-by-letsencrypt-to-new-server/31186)._