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…

Discourse + Let's Encrypt w/ multiple hostnames

Support

pfaffman (Jay Pfaffman) January 17, 2020, 11:06pm 6

Maybe have a look at Setting up Let’s Encrypt with Multiple Domains

2 Likes

Topic		Replies	Views
Nginx.http.sock not created Installation unsupported-install , nginx	3	952	July 13, 2023
Installation not working! Installation	16	1433	January 1, 2021
Moving postgres db to central db server: build error Installation	14	729	November 11, 2023
Cloudflare Tunnels - Discourse Setup Not Recognizing Hostname (Port not accessible) Installation	12	164	September 29, 2024
Discourse not loading with Apache and proxy redirect Installation	8	2335	August 14, 2020

Discourse + Let's Encrypt w/ multiple hostnames

Related topics