When migrating (via backup) a Discourse from one hostname to another, an admin might want to keep the old hostname but have the web server rewrite requests to use the new canonical name, e.g.: https://old.example.org/t/my-great-topic/12345 :arrow_heading_down: https://new.example.org/t/my-great-to…

Update: Successfully configured the secondary domain name on the standalone installation, and issued a Let’s Encrypt certificate to handle both old and new names. Precondition: I did not yet change DNS to point folks over to the new site; I wanted things to be sure to work ahead of time. So I was u…

Not Discourse-specific, but when I need to redirect over HTTPS I just redirect everything. Meaning having a server doing the redirect from the old address to the new. Some hosting options take care of this in the background, sometimes called a “domain redirect” or “forwarding” service. I don’t even…

[이미지] downey: However, the Discourse configuration passes the Discourse hostname (only) to Let’s Encrypt, and there is no concept that I can see in the Discourse configuration for aliases. Discourse will only answer to one hostname. If you want more than one hostname - where your use case, su…

[이미지] michaeld: Discourse will only answer to one hostname. Actually if you’re using a single-instance-per-server Docker-based installation, it will answer fine to any number of DNS entries (nginx is listening on port 80 and 443 for all hostnames), and correctly rewrite the URL to the canonic…

[이미지] downey: I would rather not have to maintain a separate web server just to do a rewrite rule, if possible You don’t need to, you just need an extra server section in your config.

Maybe have a look at Set up Let’s Encrypt with multiple domains / redirects

This is a perfect application for a Cloudflare rule - zero server configuration. Just throw the same URL parameters at the new domain. The orange cloud will need to be enabled for the old domain name.

[이미지] Stephen: This is a perfect application for a Cloudflare rule - zero server configuration. Just throw the same URL parameters at the new domain. Yeah, a reverse proxy situation like Cloudflare (or I suppose your own reverse proxy of choice in front of your Discourse site) could workaroun…

Discourse + Let's Encrypt, 여러 호스트네임 사용

제품 지원

pfaffman (Jay Pfaffman) 1월 17, 2020, 11:06오후 6

Set up Let’s Encrypt with multiple domains / redirects 를 참고해 보세요.

글		댓글	조회수
Multiple hostnames for a single site for cut-over phase Self-hosting	3	714	8월 31, 2023
Making 'www' work with Discourse Product Support	30	2936	5월 15, 2020
Set Up Let's Encrypt with Second Domain for Existing Discourse Install Product Support letsencrypt	5	410	3월 11, 2025
LetsEncrypt working without www, not with www Product Support	11	2103	1월 19, 2020
Set up Let’s Encrypt with multiple domains / redirects Sysadmins how-to , letsencrypt	111	21930	12월 16, 2025

Discourse + Let's Encrypt, 여러 호스트네임 사용

Related topics