# 인증서 오류 없이 non-www에서 www로 전환

**URL:** <https://meta.discourse.org/t/non-www-to-www-without-certificate-error/215022>\
**Category:** Self-hosting\
**Created:** [1월 16, 2022, 5:49오후 UTC](https://meta.discourse.org/t/non-www-to-www-without-certificate-error/215022 "2022-01-16T17:49:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)\
**Post date:** [1월 16, 2022, 6:08오후 UTC](https://meta.discourse.org/t/non-www-to-www-without-certificate-error/215022/2 "2022-01-16T18:08:04Z")

</div>

이 조언을 따라 app.yml 파일에 한 줄을 추가했습니다:

> [@Set up Let’s Encrypt with multiple domains / redirects](https://meta.discourse.org/t/setting-up-let-s-encrypt-with-multiple-domains/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…

루트 도메인이나 www 서브도메인으로 저를 찾는 데 문제가 없으므로, 리다이렉트 설정은 시도해 보지 않았습니다.

---

_[View the full topic](https://meta.discourse.org/t/non-www-to-www-without-certificate-error/215022)._