Sometime back – it’s not clear how long but at least several months – Let’s Encrypt renewals started failing on my Discourse forum, after running fine for years. When I initially noted this some days ago, the cert had expired in August 2021. After trying some manual renewals and nginx restarts, I fo…

Bingo! This problem is solved. The underlying issue was poor connectivity through a tunnel providing a single ip address associated with the Discourse forum. While tests via other sites including external ones had not shown this, your recommended test via mobile (which I should have thought of, but …

If it’s from a few months back, is it anything to do with this: [imagen] DST Root CA X3 Expiration (September 2021) Update Feb 05, 2024 It’s been two years, and the Android compatibility cross-sign mentioned below is close to expiring. See our recent blog post for a detailed explanation…

Hi. That shouldn’t relate, because that issue would cause certs to be rejected by the browser with different errors, not expired errors as in my case. It appears that Let’s Encrypt suddenly can’t authenticate with Discourse to deliver new certs. Thanks.

[imagen] JammyDodger: If it’s from a few months back, is it anything to do with this: Not if the first expiration was in August. It should have been renewing after that.

For an app not updated after june there could has been this issue though: Letsencrypt certificate failure to renew - #11 by pfaffman [imagen] L30110: However, I do not know where this data is configured into nginx for Discourse in a container and how it relates to the related nginx that proxies…

Hi. These don’t appear to apply. I’m seeing a 404 error not those other errors, the builds have been updated all along, and that template from github is indeed the version already installed in my installation. Thanks!

Are you using cloudflare with the orange cloud or some other reverse proxy?

Negative. Locally hosted on Ubuntu 18.04 using the default Docker install.

Manually running the (in container) cron job for cert renewal, the failure is always the same. The attempt to get: http://[site]/.well-known/acme-challenge/[challenge-string] fails with “Error getting validation data.”

Not being familiar with the process, could it be expecting the container to be in a state which is not the case when running that script alone? E.g. perhaps it’s expecting another cron job to occur first which prepares nginx for allowing access to such a URL. Have you tried doing a rebuild? (Which …

Hi, yes multiple rebuilds. No change. I use Let’s Encrypt on a bunch of non-discourse sites and they all renew just fine. Yes, I can access from an external site and I’ve tested using wget, the result is 404. Question: Exactly where does the nginx html tree live in this case, the part that would con…

Let's Encrypt renovaciones de certificados (de repente) fallando

Soporte Instalación

RGJ (Richard - Communiteq) 24 Diciembre, 2021 20:18 4

No, si la primera caducidad fue en agosto. Debería haberse renovado después de eso.

Tema		Respuestas	Vistas
Let's Encrypt renewal errors Self-hosting	9	1907	22 Febrero 2020
Discourse failure to renew certificate Bug letsencrypt	24	885	23 Diciembre 2025
Letsencrypt not renewing Self-hosting	5	1539	14 Julio 2017
Bootstrap error during Discourse install: ENOENT - /etc/runit/1.d/letsencrypt Self-hosting	24	483	21 Noviembre 2025
Letsencrypt certificate failure to renew Support	10	1653	8 Octubre 2021

Let's Encrypt renovaciones de certificados (de repente) fallando

Temas relacionados