# SSL is niet geldig voor www.domain.com

**URL:** https://meta.discourse.org/t/ssl-is-not-valid-for-www-domain-com/346525
**Category:** Self-hosting
**Created:** [10 januari 2025 om 15:48 UTC](https://meta.discourse.org/t/ssl-is-not-valid-for-www-domain-com/346525 "2025-01-10T15:48:17Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [10 januari 2025 om 17:44 UTC](https://meta.discourse.org/t/ssl-is-not-valid-for-www-domain-com/346525/9 "2025-01-10T17:44:30Z")

</div>

There’s a topic on this:

> [@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/ssl-is-not-valid-for-www-domain-com/346525)._