-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
certificate not renewing (finished successfully. Ongoing...) #323
Comments
Do you have files in |
Most recent entries from the staging job.json. My observation is that it didn't do anything. { |
Removing the (stale?) fqdn directories in md/stagaing seems to solve the issue. |
I had the same problem today. After deleting
If it occurs again, what would I have to do to debug it further? |
Had the same problem on FreeBSD 13.2p11, apache 2.4.59, mod_md 2.4.15. The staging/ cleanup works, but it's ugly. Where do I have to put md:debug in the apache config to get logs of the process ? |
You can add |
Our setup involves two webservers behind a load balancer. We use a script called by MDMessageCmd to synchronize (challenges and when done: full apache config) to the other node. In that script the renewed case triggers a check to see if all certificates that are being renewed are done, and only then will it reload the webserver and synchronize the apache configuration (including new certs) to the other host. My observation is that if there are leftover directories in md/staging, it's mostly from the last one being renewed. |
On a few of our servers (ubuntu 23.04, apache 2.4.55, mod_md 2.4.19) randon certificates aren't renewing.
example from the acme server status
The files in the md directory for this (redacted) fqdn still have timestamps from when the certificate was last renewed. The server status shows "finished successfully. Ongoing...". The only way I've been able to renew them is to remove the directories for the fqdn in the md directory and start over for those fqdn's. Is there a better way to do it?
The text was updated successfully, but these errors were encountered: