A user is seeking guidance on setting up Let’s Encrypt for a second domain, new.domain, on an existing self-hosted Discourse install currently using old.domain. The user is concerned about maintaining access to old.domain links during the transition and wants both domains to work simultaneously for a period. They are unfamiliar with Docker and need clear steps for running Let’s Encrypt and configuring the certificate. Other users suggest checking Discourse’s meta guides on domain changes and multi-domain Let’s Encrypt setups here and here. One user notes that adding a second domain to a Let’s Encrypt certificate is possible, though complex, and recommends using redirects from the old domain or testing on a separate instance before applying changes to the main site pfaffman.
I have forgotten how I set up Discourse initially. My questions:
where do I run let’s encrypt? Is there a script, or do I install certbot and python3-certbot-nginx somewhere? I am unfamiliar with docker, so I need a recipe or a set of steps if I have to run this in docker
once I have the certificate, how do I add the certificate to the nginx configuration?
I am switching the name of the community from old.domain to new.domain. I am hoping that the links to old.domain continue to work.
These look pretty involved. I may have to get another domain to test on another company internal Discourse install before I try it on a large public site.