Server farm? #23

New Issue

Ghost · 2018-11-08T20:28:22Z

Ghost commented

2018-11-08 20:28:22 +00:00

Some guidance for how to deal with multiple servers such that they don't all renew at same time and sharing the certificate betwixt them.

In my case the servers have a shared volume where the cert can be stored. However if Server A does the renewal and a new cert is present how can Server B discover this and therefore not attempt renewal? I am assuming a restart of Server B is necessary, does that seem correct?

Some guidance for how to deal with multiple servers such that they don't all renew at same time and sharing the certificate betwixt them. In my case the servers have a shared volume where the cert can be stored. However if **Server A** does the renewal and a new cert is present how can **Server B** discover this and therefore not attempt renewal? I am assuming a restart of **Server B** is necessary, does that seem correct?

coolaj86 commented

2018-11-08 20:34:25 +00:00

Actually, it should work just fine. The update times are random within a range (I believe between 15 and 10 days before expiration is the default) and a checkCertificate always happens just before attempting to renew a certificate.

I haven't given greenlock-cluster any love for a long while, but it specifically benefitted from (and contributed to) this design choice.

:)

Let me know if you have any troubles. How has your experience been so far?

Actually, it should work just fine. The update times are random within a range (I believe between 15 and 10 days before expiration is the default) and a `checkCertificate` always happens just before attempting to renew a certificate. I haven't given `greenlock-cluster` any love for a long while, but it specifically benefitted from (and contributed to) this design choice. :) Let me know if you have any troubles. How has your experience been so far?

Ghost commented

2018-11-08 21:01:13 +00:00

That's great. Nice job with all of this.
My experience so far has been good.
I'll let you know if I run into anything.

That's great. Nice job with all of this. My experience so far has been good. I'll let you know if I run into anything.

Ghost closed this issue

2018-11-08 21:01:13 +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: coolaj86/greenlock.js-ARCHIVED#23