I hope someone can offer some advice, I would be in your debt. I’ll explain the situation.
I’ve set up Discourse many times on my domain, hostballs[.]com. Each time visiting www[.]hostballs[.]com will nicely redirect to hostballs[.]com, because the LetsEncrypt certificate covers both with and without www. This is what I’ve come to know as the default, standard behavior of Discourse with it’s LE implementation.
Currently, my new Discourse install is setting up SSL for the non-www site (as is configured as the URL), but it isn’t covering www. This means anyone visiting www[.]hostballs[.]com will not be redirected, but instead see an SSL error. Given that I know the default behavior to vary from this, and that Discourse’s installation is far too controlled for me to just want to run to certbot and start doing it all manually (won’t that make updating regularly fun), I’m uncertain of the best path forward.
While trying to resolve this I commented out the ssl and LE templates, as well as the LE email address, in app.yml. I then removed the letsencrypt and ssl directories from /shared/standalone. I rebuilt the site without SSL, then re-enabled those options in app.yml and rebuilt again to generate new SSL certs/configs. While this succeeded, it still did not correct the www issue.
Has anyone else dealt with a similar situation and found a resolution?