Hi there, I would like to make sure the www subdomain redirects the users to the actual Discourse install. I feel like this needs to be the case to ensure I don’t lose visitors. Most people don’t leave out the ‘www’ when visiting websites.

You need to add an A record in your DNS settings at your registrar for www pointing to the server’s IP. The same one you are currently pointing the domain.com A record to.

Will this cause issues when the user visits using the www version? Discourse is set to not have the www included.

No because the user will be redirected. It won’t serve the same site under multiple domains.

You want these guides. I used them for the same exact purpose: [图片] (Superseded) Redirect additional domain(s) to your Discourse instance Self-Hosting warning 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… [图片] Set up Let’s Encrypt with multiple domains / redirects Sysadmins 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…

Are you saying adding the A record for ‘www’ isn’t enough? I read through those articles.

My site would get a nasty message on the browser without registering a certificate for both “sub-domains”.

I’ve just set up Discourse on a Digital Ocean droplet. For step 2, editing discourse.conf, does that require nginx to be installed? I’m not certain but I don’t think my droplet has nginx installed and I’m at a loss with how to install it.

I think this guide explains that part: https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247/294

Yes adding an a record for www aimed at the same IP will be adequate to redirect the traffic. You don’t need to do anything outlined in those other guides, an A record pointed to the IP will suffice for a simple redirect. Try not to complicate your install unless absolutely necessary.

Will this be enough to avoid a NET::ERR_CERT_COMMON_NAME_INVALID browser error though? If I install discourse on the www subdomain, accessing the site with https://example.com gives me that error. It only works if you use https://www.example.com.

让“www”在 Discourse 中正常工作

产品支持

merefield (Robert) 2020 年5 月 8 日 06:04 5

你需要这些指南。我正是出于完全相同的目的使用过它们：

话题		回复	浏览量
Non www to www without certificate error Self-hosting	13	2146	2022 年1 月 17 日
Www.example.com OK, but example.com NOT Self-hosting	3	1205	2019 年9 月 4 日
Correct DNS records to set when Discourse is hosted on WWW subdomain? Self-hosting	2	1263	2020 年5 月 9 日
LetsEncrypt working without www, not with www Product Support	11	2130	2020 年1 月 19 日
About force www to non www Product Support	29	3085	2019 年1 月 6 日

让“www”在 Discourse 中正常工作

相关话题