# לא www ל-www ללא שגיאת אישור **URL:** https://meta.discourse.org/t/non-www-to-www-without-certificate-error/215022 **Category:** Self-hosting **Created:** [16 בינואר,‏ 2022,‏ 5:49pm 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:** 9
### Author: ![Elmi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elmi/32/246479_2.png) [@Elmi](https://meta.discourse.org/u/Elmi) #### Post date: [16 בינואר,‏ 2022,‏ 10:57pm UTC](https://meta.discourse.org/t/non-www-to-www-without-certificate-error/215022/9 "2022-01-16T22:57:56Z")
Just a quick update to let you know what worked for me. I tried, but this didn’t worked for me.It looked like no additional certificate was issued. > [@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… I also tried to solve my issue by following this suggestion, but this also didn’t work for me. > [@Setup Let’s Encrypt + non-www \> www](https://meta.discourse.org/t/let-s-encrypt-non-www-www/84840): > > I finally made it work, and thought to put everything together in case someone needs it. This info is assembled from different topics on this forum. Thanks to @brahn and @techAPJ. This assumes you’ve completed the initial Let’s Encrypt setup: After you’ve done it, the following needs to be added to the app.yml in hooks section. It will do two things: setup SSL for both example.com and www.example.com. Just replace example.com with your domain name. redirect example.com to www.example.com I… The only thing which solved my issue so far was by following the instructions here [http://www.forcewww.com/](http://www.forcewww.com/) Nevertheless, I think this is still not a desirable solution, as it relies on an external service. Of course, it is free of charge, but you’ll need to find a new solution once this service is down. I hope you don’t get me wrong @michaeld , it’s really a nice and easy solution which you are offering and I highly appreciate it. It would be pretty cool thing, if you could decide during the [standard install](https://meta.discourse.org/t/142537?silent=true) to go only with a www or non www version to make our life a little bit easier 🙂 --- _[View the full topic](https://meta.discourse.org/t/non-www-to-www-without-certificate-error/215022)._