Error de certificado de no www a www

[JammyDodger]

I followed this advice, and added a line to my app.yml:

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…

Though I don’t mind if people find me on the root domain or the www subdomain, so I haven’t tried it with redirects.