I have set up my Discourse community with Digital Ocean, but the domain name is “naked”, at just https://example.com . I would like to add the www., but not quite sure what I am doing when it comes to DNS settings! At the moment I have an ‘A’ record pointing to the IP and a ‘CNAME’ record with www. …

I think that’s how it works. :+1:

First off, create a DNS record like: TYPE: CNAME HOST: WWW POINTS TO: @ Then follow this guide: [이미지] Change the domain name or rename your Discourse Self-Hosting bookmark This guide explains how-to change the domain name of yo…

Thank you very much for this - I have successfully got it working at the www. by re-running the discourse-setup script as in your article, but now the naked domain no longer works! Is there any way I can make the naked domain work as well - or at least automatically fill in the www.? So I now have …

The easy way is forcewww.com . Harder is Setting up Let’s Encrypt with Multiple Domains .

Thank you for this - I have read through both options, but just wondered, why could I not just use a simple 301 redirect to redirect from naked domain to www.? Is this worth a try or am I breaking DNS laws?

Both of those methods provide a letsencrypt certificate for the second (sub)domain. Adding the extra info to your app.yml covers both domain addresses in the same certificate, and forcewww.com has some special magic that does it on the fly so you don’t have to worry about it:

O.K sounds as if I should just use forcewww. Can I just confirm (sorry I am very out of my depth) - they are asking me to set up the www as an A record to my server IP, and the naked domain as an A record to the IP address they give? So no CNAMES? What I have now: A record pointing naked domain to…

Thanks! I have set it up - not working yet (typing in naked domain) but it may take a few hours to take effect so will wait and see!

Yay I think it works! Thank you very much for all your help!

Unfortunately - this has somehow broken the emailing system - the site is not sending any emails through mailgun. Might this be because of the forcewww - as the host is now through their server? Or do I need to update mailgun to say www? Lord give me strength.

You need to change the DISCOURSE_NOTIFICATION_EMAIL to noreply@baredomain.com. I’d edit the yml and destroy and start the container.

도메인에 www. 추가하기

제품 지원 자체 호스팅

pfaffman (Jay Pfaffman) 3월 19, 2022, 3:51오후 4

가장 쉬운 방법은 forcewww.com을 사용하는 것입니다. 좀 더 어려운 방법은 여러 도메인으로 Let’s Encrypt 설정하기입니다.

글		댓글	조회수
Making 'www' work with Discourse Product Support	30	2931	5월 15, 2020
Www.example.com OK, but example.com NOT Self-hosting	3	1194	9월 4, 2019
How to install Discourse in WWW Self-hosting	3	1215	12월 2, 2020
Correct DNS records to set when Discourse is hosted on WWW subdomain? Self-hosting	2	1255	5월 9, 2020
How can I enable www subdomain Self-hosting	9	1505	3월 29, 2019

도메인에 www. 추가하기

Related topics