Non www to www without certificate error

[Elmi (Ekmo)]

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

This is to address the problem where you get certificate errors with any redirects or CNAME DNS entries which point to your actual installed Discourse (sub)domain. If you do not have https configured already (you do if you have done a standard install recently) see Setting up Let’s Encrypt as your first step. There are two patterns that need to be replaced, one ending in --keylength, and another ending in --fullchainpath (in the actual file, your original domain is before each of these switche…

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

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/

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 to go only with a www or non www version to make our life a little bit easier