# Set up Let’s Encrypt with multiple domains / redirects

**URL:** <https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685>\
**Category:** Sysadmins\
**Tags:** how-to, letsencrypt\
**Created:** [February 1, 2017, 2:21am UTC](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685 "2017-02-01T02:21:03Z")\
**Posts on this page:** 1\
**Showing post:** 176

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [August 20, 2025, 2:27pm UTC](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685/176 "2025-08-20T14:27:34Z")

</div>

> [@Paul\_King](#):
>
> Would be even better if there was some clever way for discourse to write the aliases supplied by admin to app.yml itself when next updating,

Not likely. It’s the kind of thing that you’re likely to do exactly once, and you’ll do it when you’re already mucking with `app.yml`.

I’ll see about making a PR that adds it to the `standalone.yml`, though.

[https://github.com/discourse/discourse\_docker/pull/995](https://github.com/discourse/discourse_docker/pull/995)

And with this in place, this is much simpler!

---

_[View the full topic](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685)._