autorenewal certificates doesn't work #37

Closed
opened 2020-03-30 16:02:04 +00:00 by Ghost · 2 comments

We use V3 and V4 greenlock-express for our setups.
We didn't configure renewOffset. So I assume -45d default is used?

All of our services running greenlock-express neglected to update their certificates unless I restart the complete service.

We use V3 and V4 greenlock-express for our setups. We didn't configure renewOffset. So I assume -45d default is used? All of our services running greenlock-express neglected to update their certificates unless I restart the complete service.
Owner

Yes, renewOffset is -45d by default.

Do you have any logs or other info that might help in diagnosing this?

Yes, `renewOffset` is -45d by default. Do you have any logs or other info that might help in diagnosing this?
Author

@solderjs Not a problem with greenlock, we got the warning emails from letsencrypt although a new certificate is already created.

@solderjs Not a problem with greenlock, we got the warning emails from letsencrypt although a new certificate is already created.
Ghost closed this issue 2020-05-28 12:50:41 +00:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: root/greenlock-express.js#37
No description provided.