Let's Encrypt funziona senza www, ma non con www

[merefield (Robert)]

Certo! È un po’ di lavoro in più, ma è semplice e un caso d’uso molto comune. Vedi:

Set up Let’s Encrypt with multiple domains / redirects

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…

E poi:

(Superseded) Redirect additional domain(s) to your Discourse instance

2024-04-09 @pfaffman edited this to say that this is no longer necessary, as the current NGINX config in the standard install redirects everything to https://HOSTNAME. You can test this by entering your IP address and see that it gets redirected. If you want multiple domains pointed to your server, you probably want them to have valid https certificates. To do that, follow instructions at Set up Let’s Encrypt with multiple domains / redirects. So you want to redirect domain(s) to yo…