# After activating HTTPS Discourse doesn´t work

**URL:** https://meta.discourse.org/t/after-activating-https-discourse-doesn-t-work/206907
**Category:** Self-hosting
**Created:** [October 24, 2021, 5:45pm UTC](https://meta.discourse.org/t/after-activating-https-discourse-doesn-t-work/206907 "2021-10-24T17:45:38Z")
**Posts on this page:** 1
**Showing post:** 18

<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: [October 28, 2021, 9:07am UTC](https://meta.discourse.org/t/after-activating-https-discourse-doesn-t-work/206907/18 "2021-10-28T09:07:00Z")

</div>

Can you add [http://deinbalkonnetz.de/](http://deinbalkonnetz.de/) as a second domain to the letsencrypt certificate as a possible workaround?

> [@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…

---

_[View the full topic](https://meta.discourse.org/t/after-activating-https-discourse-doesn-t-work/206907)._