-
Notifications
You must be signed in to change notification settings - Fork 101
Let's Encrypt doesn't auto renew #48
Comments
Hmm, that sounds like a bug. It already has cron installed into the container, and the cron daemon is supposed to run every week to renew the certificates where needed:
If you run |
I can confirm that script exists on the new image and appears to be correct. I can also confirm cron is running in the new container. Docker seems to have garbage collected the old container so I can't look at the failed instance. I'm happy to provide any logs if this happens again on the current container. The image ID is |
Sure, if it does happen again, can you check that:
|
Docker images:
Should I just do |
This should be fixed with the latest merged PR. I suggest waiting a little while for the Docker Hub to build the new image, then running |
And no, you can do |
For my instance it's enough to |
My phabricator instance needed to be bounced today because the Let's Encrypt certificate had expired. Is there already a mechanism to auto renew Let's Encrypt certs? If not, what's the best way to add one? I bet that Phabricator already has some kind of cron like service installed, but how to use it?
The text was updated successfully, but these errors were encountered: