coolaj86
/
greenlock.js-ARCHIVED
3
3
Fork 0
Code Issues 13 Pull Requests 1 Releases Activity
Labels Milestones
New Issue

Is there a way to force a certificate renewal? #32

Closed
by Ghost opened 5 years ago · 1 comments
Ghost commented 5 years ago

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!

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](https://git.coolaj86.com/coolaj86/greenlock.js#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!
coolaj86 commented 5 years ago
Owner

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 to le-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).

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` to `le-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).
coolaj86 closed this issue 5 years ago
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
acmev2
dns-challenge-regression-fix
github
greenlock
master
next
node-letsencrypt-python
npm
v1
v2
v2.1
v2.2
v2.3
v2.4
v2.5
v3
v4
wip
Labels
Apply labels
Clear labels
No items
No Label
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(MISSING)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes