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
Making 'www' work with Discourse support	30	1858	May 15, 2020
Redirect additional domain(s) to your Discourse instance sysadmin how-to	87	21723	April 9, 2024
Problem in installing Let's Encrypt SSL for www and non-www installation	12	4281	September 8, 2023
Using a certificate when Discourse is installed behind a reverse proxy installation unsupported-install	24	4353	May 17, 2019
Discourse setup script hostname validation for Let's Encrypt dev	14	1095	February 20, 2020

Discourse + Let's Encrypt w/ multiple hostnames

Related Topics