Is there a way to force a certificate renewal? #32
Etiketler
Etiket Yok
Kilometre Taşı Yok
Atanan Kişi Yok
2 Katılımcı
Bildirimler
Bitiş Tarihi
Bitiş tarihi atanmadı.
Bağımlılıklar
Bağımlılık yok.
Referans: coolaj86/greenlock.js-ARCHIVED#32
Yükleniyor…
Yeni konuda referans
Herhangi bir açıklama sağlanmadı.
"%!s(<nil>)" Dalını Sil
Bir dalı silmek kalıcıdır. Her ne kadar silinen dal tamamen kaldırılana kadar çok kısa bir süre yaşamını sürdürse de, çoğu durumda bu işlem GERİ ALINAMAZ. Devam edilsin mi?
One of my production servers using greenlock is not automatically renewing its certificate, and I would like to "force" it, and/or figure out what is wrong. Is there an API or method I can call to trigger the renewal?
I'd also like to capture the result, to see what the error is, if any. I can't find any logs for greenlock (the log directory is empty), so I don't know if it has attempted renewal and failed, or simply isn't attempting it at all.
Related, if I use your Manual HTTPS method, does the
greenlock.register()
method actually re-register the certificate each time it is called? I wonder if I should just call that at startup.Thanks!
Sorry for the late response.
The best way to force it is to remove the certificate from the file system and restart.
I just did a whole boat load of cleanup, so if you update to v2.7 and switch from using
le-store-certbot
tole-store-fs
( usage can be seen at https://git.coolaj86.com/coolaj86/greenlock-express.js/src/branch/master/examples/wildcard.js ), I'd be interested to know if that alone fixes it.If you were using
le-store-certbot
before (the default), it really sucked at multiple-domains on a single certificate due to legacy code...The new soon-to-be-default store plugin shouldn't have those problems (and should serve as a much better example for building your own).