I hope someone can offer some advice, I would be in your debt. I’ll explain the situation. I’ve set up Discourse many times on my domain, hostballs[.]com. Each time visiting www[.]hostballs[.]com will nicely redirect to hostballs[.]com, because the LetsEncrypt certificate covers both with and witho…

Easiest fix for someone using their root domain and wanting www to be signed by LE for proper https redirect without overcomplicating it or using another web server to manage the redirect: Change this: issue_cert() { LE_WORKING_DIR=“${LETSENCRYPT_DIR}” $$ENV_LETSENCRYPT_DIR/acme.sh --issue $2 -d…

Sure! This is a little extra work but straightforward and a very common use case. See: [صورة] 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 l…

If the above advice is too intimidating you could also set up a simple DNS redirect. Most registrars offer this. Discourse can’t be published under multiple URLs, the root record (non www) and www ‘a’ record are separate addresses. Once you nominate an FQDN for your site any additional addresses ne…

If you don’t like either of the suggestions provided already, you can opt to use www.example.com and use http://forcewww.com/ to redirect to the www site.

Thank you friends. Let me go over some details that might help someone else in the future. This started because a user told me that visiting www didn’t work, it gave a certificate error. When directly visiting their https link they provided in the reporting thread, I met the same. In the past when …

Yes, anything which hits the IP of your server on port 80 will be redirected to the actual FQDN over HTTPS, www isn’t a special case.

That isn’t a solution, the changes will be eradicated whenever templates are updated and for that reason alone is inadvisable. If you want to modify files within the container use hooks in your app.yml

Aye, I’m not seeing a way to achieve it that doesn’t have the potential to be broken on updates. This just seems to be the plight of people who have dedicated domains for communities and don’t like unnecessary subdomains. Short of running another web server elsewhere, of course.

Guides already exist for modifying certificate enrolment if you use the search.

Right, I’m already seeing one attempt that was then halted by a file changing so it broke the way they were setting it up to change the file in app.yml: [صورة] Problem in installing Let's Encrypt SSL for www and non-www Self-hosting Similar situation here. I i…

My point is that any change to that template will break it again. Only one change has broken the PUPS/hooks method in the last few years, the introduction of support for ECC.

Let's Encrypt يعمل بدون www، ولا يعمل معه

دعم المنتج

merefield (Robert) 18 يناير 2020، 9:02ص 2

بالتأكيد! هذا يتطلب جهدًا إضافيًا قليلًا لكنه مباشر، وهو حالة استخدام شائعة جدًا. راجع:

ثم:

الموضوع		الردود	مرات العرض
Problem in installing Let's Encrypt SSL for www and non-www Self-hosting	10	4958	3 ديسمبر 2019
Non www to www without certificate error Self-hosting	13	2133	17 يناير 2022
SSL working on root, but not on www Product Support	28	4669	30 ديسمبر 2021
About force www to non www Product Support	29	3076	6 يناير 2019
Making 'www' work with Discourse Product Support	30	2988	15 مايو 2020

Let's Encrypt يعمل بدون www، ولا يعمل معه

الموضوعات ذات الصلة