# Setup Let’s Encrypt + non-www \> www

**URL:** https://meta.discourse.org/t/setup-let-s-encrypt-non-www-www/84840
**Category:** Sysadmins
**Tags:** how-to, domains
**Created:** [4월 8, 2018, 10:33오후 UTC](https://meta.discourse.org/t/setup-let-s-encrypt-non-www-www/84840 "2018-04-08T22:33:44Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![tomtjes](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tomtjes/32/131271_2.png) [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [2월 23, 2025, 1:04오전 UTC](https://meta.discourse.org/t/setup-let-s-encrypt-non-www-www/84840/9 "2025-02-23T01:04:09Z")

</div>

이 방법이 더 이상 작동하지 않고 인스턴스에 접근할 수 없게 만드는 것 같습니다. 대신 다음 방법을 사용하여 다시 정상 작동하도록 했습니다:

> [@Set up Let’s Encrypt with multiple domains / redirects](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685):
>
> NOTE: @pfaffman says: This page needs to be cleaned up. There is now a new ENV setting that will let you add more hostnames. In your app.yml under your DISCOURSE\_HOSTNAME line (it can go many places but that one makes sense), add DISCOURSE\_HOSTNAME\_ALIASES: domain.com,other.domain.com and early reports suggest that you’ll get valid certs for those domains and that accessing https://domain.com will properly redirect you to your DISCOURSE\_HOSTNAME without a certificate error. If you do that an…

---

_[View the full topic](https://meta.discourse.org/t/setup-let-s-encrypt-non-www-www/84840)._