# Let's Encrypt 1주 제한에 대한 임시 해결책

**URL:** https://meta.discourse.org/t/workaround-for-the-1-week-lets-encrypt-limit/268586
**Category:** Self-hosting
**Created:** [6월 16, 2023, 7:24오전 UTC](https://meta.discourse.org/t/workaround-for-the-1-week-lets-encrypt-limit/268586 "2023-06-16T07:24:55Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![tmc1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tmc1/32/311566_2.png) [@tmc1](https://meta.discourse.org/u/tmc1)
#### Post date: [6월 16, 2023, 7:24오전 UTC](https://meta.discourse.org/t/workaround-for-the-1-week-lets-encrypt-limit/268586/1 "2023-06-16T07:24:55Z")

</div>

여러분 안녕하세요!

Discourse를 설치하려고 시도하고 있는데, 재빌드 몇 번 후에 아래 이유로 웹사이트가 로딩되지 않고 있습니다:

[https://letsencrypt.org/docs/duplicate-certificate-limit/](https://letsencrypt.org/docs/duplicate-certificate-limit/)

우회 방법에서 설명하듯, 새로운 도메인 세트를 요청하여 이 제한을 우회하고 1주일 기다리지 않아도 되는 방법이 있을까요? Ubuntu Vultr에서 배포하고 있습니다.

감사합니다

---

<div class="post-metadata">

### Author: ![tmc1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tmc1/32/311566_2.png) [@tmc1](https://meta.discourse.org/u/tmc1)
#### Post date: [6월 16, 2023, 7:51오전 UTC](https://meta.discourse.org/t/workaround-for-the-1-week-lets-encrypt-limit/268586/2 "2023-06-16T07:51:17Z")

</div>

지금은 서브도메인을 사용하여 다시 빌드(rebuild)를 해보고 이제 작동하는지 확인해 보았습니다.

도메인으로 다시 전환하려면 다시 빌드만 하면 되나요? 모든 영구 링크(permalinks) 등이 자동으로 업데이트되나요?

원하는 경우 두 가지를 동시에 유지할 수 없는 것 같죠?

감사합니다.

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [6월 16, 2023, 8:50오전 UTC](https://meta.discourse.org/t/workaround-for-the-1-week-lets-encrypt-limit/268586/3 "2023-06-16T08:50:55Z")

</div>

참고:

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

그리고

> [@(Superseded) Redirect additional domain(s) to your Discourse instance](https://meta.discourse.org/t/redirect-additional-domain-s-to-your-discourse-instance/18492):
>
> warning 2024-04-09 @pfaffman edited this to say that this is no longer necessary, as the current NGINX config in the [standard install](https://meta.discourse.org/t/142537?silent=true) redirects everything to https://HOSTNAME. You can test this by entering your IP address and see that it gets redirected. If you want multiple domains pointed to your server, you probably want them to have valid https certificates. To do that, follow instructions at [Set up Let’s Encrypt with multiple domains / redirects](https://meta.discourse.org/t/set-up-let-s-encrypt-with-multiple-domains-redirects/56685). So you want to redirect domain(s) to yo…
