If, for any reasons (e.g. due to the failing migrations requiring re-installations or any other “experimenting”) you have to perform a few subsequent rebuild-app’s, what would be the safest way to ensure the already existing Let’s Encrypt cert is re-used and not re-issued? As I understand (this is what I saw in some post here), after a few tries Let’s Encrypt blocks your cert for some time (days?), hence the question.

Rebuild should not reissue a certificate every time, only when it is due for renewal, If you are wiping the server and then re-installing discourse then it will become a problem.

Are you sure? I mean, “should not” or “will not”? In my case after probably the 4th discourse-setup within the same existing installation the server finally started to “time-out” (for a few days). There are many posts here advising to use ./discourse-setup when you need to modify setup details, emails etc. There are those 3 lines in the app.yml: ## Uncomment these two lines if you wish to add Lets Encrypt (https) - "templates/web.ssl.template.yml" - "templates/web.letsencrypt.ssl.template.yml" but I’m not sure whether commenting them out means the existing cert will be left/reused or there will be no cert at all.

Re-installing and Let's Encrypt

Product Support Self-hosting

pfaffman (Jay Pfaffman) March 22, 2024, 6:53pm 4

Did it work and got a certificate and you didn’t change the hostname after that?

You get no cert if you comment them out.

Topic		Replies	Views
Unable to renew Let's encrypt certificate Self-hosting letsencrypt	7	1188	February 7, 2024
Can’t get certificate to work? Self-hosting letsencrypt	2	595	October 23, 2023
Letsencrypt issued on every build? Product Support	7	1536	February 28, 2022
Discourse failure to renew certificate Bug letsencrypt	24	1353	December 23, 2025
Hit Let's encrypt renewal limit Self-hosting	6	2334	July 1, 2020

Re-installing and Let's Encrypt

Related topics