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 …

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…

I couldn’t find a cron job, just a runlevel script at /etc/runit/1.d/letsencrypt. It looks like that script starts a new instance of nginx with a config which includes this: location ~ /.well-known { root /var/www/discourse/public; allow all; } I think that means the path would end up being /v…

I think I may see the problem. But I don’t know how to fix it. It appears that all attempts to access the forum on https port 80 are (as expected) being redirected https 443. Right. But this means that when Let’s Encrypt attempts to validate for the renewal, it fails, because the current certificate…

This redirect is in /etc/nginx/conf.d/discourse.conf and will not be used when nginx is stopped, then started with the config mentioned in my previous post. I’m afraid I’m not very familiar with how the auto-upgrade works so I’m not sure what the appropriate method would be to renew while the conta…

And indeed this does permit Let’s Encrypt to get in without the redirect, but apparently the file it’s looking for does not exist, so ultimately the same verification failure.

I have the same problem. Has anyone worked out a clear procedure the correct the problem?

I’m now using this to try successfully get the cert. It appears that the validation token IS being retrieved by curl, but acme.sh is STILL declaring a validation failure every time! So still down. “/shared/letsencrypt”/acme.sh --renew-all --force --insecure --home “/shared/letsencrypt” --debug

Hi @L30110 :slightly_smiling_face: I’m one of the regulars over in the Let’s Encrypt community . I was sent by @JimPas to take a look into this thread, which I will do as soon as I return from lunch.

Let's Encrypt-Zertifikat-Erneuerungen schlagen (plötzlich) fehl

Unterstützung Installation

mbronstein (Mark Bronstein) 27. Dezember 2021 um 16:51 16

Ich habe dasselbe Problem. Hat jemand ein klares Verfahren zur Behebung des Problems gefunden?

2 „Gefällt mir“

Thema		Antworten	Aufrufe
Let's Encrypt renewal errors Self-hosting	11	1873	22. Februar 2020
Discourse failure to renew certificate Bug letsencrypt	25	712	27. Dezember 2025
Letsencrypt not renewing Self-hosting	6	1505	8. Juni 2024
Bootstrap error during Discourse install: ENOENT - /etc/runit/1.d/letsencrypt Self-hosting	24	354	21. November 2025
Letsencrypt certificate failure to renew Support	11	1616	8. Oktober 2021

Let's Encrypt-Zertifikat-Erneuerungen schlagen (plötzlich) fehl

Verwandte Themen