coolaj86/greenlock.js-ARCHIVED
3
3
Derivar 0
Código Questões 6 Pedidos de integração 1 Lançamentos Trabalho

Automatic renewal #26

Questão nova
fechada(s)
2018-12-06 15:00:58 +00:00 aberta(s) por Ghost · 3 comentários
Ghost comentou 2018-12-06 15:00:58 +00:00
Copiar ligação

Hi, well done 👍

How automatic renewal works? Does it kind of a cron job?

Or should I call the register method every month to ensure my certificates renewed?

Hi, well done :+1: How automatic renewal works? Does it kind of a cron job? Or should I call the `register` method every month to ensure my certificates renewed?
coolaj86 comentou 2018-12-06 17:12:10 +00:00
Proprietário(a)
Copiar ligação

Each certificate has an expiry time listed on the certificate which is cached and checked on each new tls session request.

When the certificate is less than 15 days from expiring, register is automatically called (with a random jitter to prevent simultaneous renewal on high-traffic sites).

There’s nothing that you have to do. :)

Each certificate has an expiry time listed on the certificate which is cached and checked on each new tls session request. When the certificate is less than 15 days from expiring, register is automatically called (with a random jitter to prevent simultaneous renewal on high-traffic sites). There’s nothing that you have to do. :)
Ghost comentou 2018-12-06 18:01:47 +00:00
Autor(a)
Copiar ligação

Thank you for your quick response.

So it means if there is no traffic for more than 90 days, they will be expired. Am I right?

And I don't use the default middleware. Instead, I've got my own SNICallback. I think in this use-case, the renewal process won't work.

Thank you for your quick response. So it means if there is no traffic for more than 90 days, they will be expired. Am I right? And I don't use the default middleware. Instead, I've got my own SNICallback. I think in this use-case, the renewal process won't work.
coolaj86 comentou 2018-12-06 23:45:37 +00:00
Proprietário(a)
Copiar ligação

That's correct. This was built assuming a public-facing webserver with daily traffic. However, if I recall correctly, it will wait until the certificate has renewed until responding to the request if the cert is expired.

What's your use case?

Dipping down into the SNICallback is certainly valid, but there may be a way to do what you need to do and still take advantage of the built-in niceties (maybe by calling greenlock's SNICallback after you do what you need to do).

That's correct. This was built assuming a public-facing webserver with daily traffic. However, if I recall correctly, it will wait until the certificate has renewed until responding to the request if the cert is expired. What's your use case? Dipping down into the SNICallback is certainly valid, but there may be a way to do what you need to do and still take advantage of the built-in niceties (maybe by calling greenlock's SNICallback after you do what you need to do).
coolaj86 encerrou esta questão 2019-02-05 05:14:07 +00:00
Inicie a sessão para participar neste diálogo.
Sem ramo ou etiqueta especificados
Ramos Etiquetas
Rótulos
Sem itens
Sem rótulo
Etapa
Sem itens
Sem etapa
Encarregados
Retirar todos os encarregados
jshaver coolaj86
Sem encarregados
2 Participantes
Notificações
Data de vencimento
Sem data de vencimento definida.
Dependências

Não estão definidas dependências.

Referência: coolaj86/greenlock.js-ARCHIVED#26
Nenhuma descrição fornecida.
Eliminar o ramo "%!s()"

Eliminar um ramo é algo permanente. Embora o ramo eliminado possa continuar a existir por um breve período de tempo antes de ser realmente removido, a operação NÃO PODERÁ ser desfeita na maioria dos casos. Quer continuar?