# Www to non www with https

**URL:** https://meta.discourse.org/t/www-to-non-www-with-https/284916
**Category:** Support
**Created:** [November 9, 2023, 8:27am UTC](https://meta.discourse.org/t/www-to-non-www-with-https/284916 "2023-11-09T08:27:01Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [November 9, 2023, 8:58am UTC](https://meta.discourse.org/t/www-to-non-www-with-https/284916/3 "2023-11-09T08:58:31Z")

</div>

Yep that’s your first and main problem, see:

> [@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/www-to-non-www-with-https/284916)._