# Discourse failure to renew certificate

**URL:** https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148
**Category:** Bug
**Tags:** letsencrypt
**Created:** [October 9, 2025, 3:38pm UTC](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148 "2025-10-09T15:38:48Z")
**Posts on this page:** 6
**Page:** 2

<div class="post-metadata">

### Author: ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [December 22, 2025, 6:59pm UTC](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148/22 "2025-12-22T18:59:13Z")

</div>

Ah thanks for the confirmation and the reports - Nat was able to triage this and found there was a quote in the script that needed escaping. Let us know if the next renewal goes better.

---

<div class="post-metadata">

### Author: ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy)
#### Post date: [December 22, 2025, 9:17pm UTC](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148/24 "2025-12-22T21:17:14Z")

</div>

Do we need to update or rebuild ?

---

<div class="post-metadata">

### Author: ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [December 22, 2025, 11:27pm UTC](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148/25 "2025-12-22T23:27:46Z")

</div>

Yes, a rebuild will be necessary to inherit the new configuration for this

---

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [December 23, 2025, 5:33pm UTC](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148/26 "2025-12-23T17:33:44Z")

</div>

So, over the next three months, we can expect a rash of self-hosters seeing failed certificate renewal, if they last updated before this bug was introduced and haven’t yet updated since yesterday’s fix?

Can I suggest this is highlighted in the next regular release?

(For myself, my certs expire late Jan, and my installations, updated to the 2025-12-latest in late Nov, do have the bug.)

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [December 23, 2025, 10:29pm UTC](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148/27 "2025-12-23T22:29:57Z")

</div>

I think it’s still true that if you rebuild you get a new cert and it’s unlikely that we’ll go three months without an update that requires a rebuild. But if you’re someone who doesn’t do command line upgrades then you’ll likely get a cert error. This bug has been around in various ways for most of this year.

---

<div class="post-metadata">

### Author: ![nat](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nat/32/235063_2.png) [@nat](https://meta.discourse.org/u/nat)
#### Post date: [December 27, 2025, 12:00am UTC](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148/29 "2025-12-27T00:00:29Z")

</div>

This topic was automatically closed after 4 days. New replies are no longer allowed.

[Previous page](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148.md?page=1)
