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.

That’s why you want to use a redirect, discourse can’t be served from multiple URLs. Pick one, redirect the other.

I have a similar issue and using a URL redirect record at the DNS level doesn’t solve the problem for me. I installed Discourse using the hostname ‘ www.example.com ’ and the following DNS records: A Record host:WWW value:my_server_ip CNAME host:@ value: www.ex…

Hence why I posted those links. I’d love it to be as simple as a DNS change. It didn’t seem to be that simple to me either. To work via https I had to ensure that a cert was being registered for both addresses. To achieve that use one of the guides I posted above. The other guide allows you to p…

Users are very unlikely to specify the protocol when typing in a URL. If you’re really worried about it you can just use Cloudflare for DNS and a simple page rule.

Yeah, I ‘moved’ my domain (well I just chose to cut off the www) which is why I had to serve existing links already on sites I didn’t control referring to my old domain with https. That might explain why in my case I had no choice but to do the full job. So what I think you are saying is, if you a…

Or just use a page rule as stated above. It will front the domain using a wildcard cert and redirect the traffic seamlessly. All with zero additional complexity on the Discourse server.

[imagen] Stephen: Or just use a page rule What’s a page rule? I’m intending to follow How To Install Discourse Behind Nginx on Ubuntu 14.04 | DigitalOcean to install Nginx on my Digital Ocean droplet and then apply the rules listed in “step 2” to redirect to the correct domain. I think this …

@Erik_Manger , DNS-based solutions didn’t work for me with SSL. I used the first link provided by @merefield and it works well.

Did you need to install Nginx in-front of Discourse to get this to work? On my Digital Ocean droplet the path “/etc/nginx/” used in the additional hooks doesn’t exist.

Nope, no additional install. Also, the only block I needed to add is: after_ssl: - replace: filename: "/etc/runit/1.d/letsencrypt" from: /--keylength/ to: "-d mywebsite.org --keylength" (http to https redirect seems to be working fine without the two other replace bl…

Hacer que 'www' funcione con Discourse

Soporte del producto

syl 14 Mayo, 2020 15:22 19

@Erik_Manger, las soluciones basadas en DNS no funcionaron para mí con SSL. Usé el primer enlace proporcionado por @merefield y funciona bien.

Tema		Respuestas	Vistas
Non www to www without certificate error Self-hosting	13	2100	17 Enero 2022
Www.example.com OK, but example.com NOT Self-hosting	3	1197	4 Septiembre 2019
Correct DNS records to set when Discourse is hosted on WWW subdomain? Self-hosting	2	1256	9 Mayo 2020
LetsEncrypt working without www, not with www Product Support	11	2110	19 Enero 2020
About force www to non www Product Support	29	3064	6 Enero 2019

Hacer que 'www' funcione con Discourse

Temas relacionados