You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, the "days" value used during "issue" is stored in the domain.conf along with the next renewall timestamp/date. there seems currently no way to automatically adjusting this values.
I'm trying to lower the renewall days from the initial 80 to 70 to avoid getting the "Let's Encrypt certificate expiration notice" email notifications. I was hoping I could just use the --days parameter with --renew resp. --renewAll to have the values adjusted when the certificates are due to renew, but acme.sh keeps using the initial 80 days as stored in the domain conf.
it would be nice to have the following:
--renew and --renewAll recognise the --days parameter
(optionally) if the passed --days value is different from what is stored in the domain conf recalculate the Le_NextRenewTime and Le_NextRenewTimeStr values
The text was updated successfully, but these errors were encountered:
currently, the "days" value used during "issue" is stored in the domain.conf along with the next renewall timestamp/date. there seems currently no way to automatically adjusting this values.
I'm trying to lower the renewall days from the initial 80 to 70 to avoid getting the "Let's Encrypt certificate expiration notice" email notifications. I was hoping I could just use the
--days
parameter with --renew
resp.--renewAll
to have the values adjusted when the certificates are due to renew, but acme.sh keeps using the initial 80 days as stored in the domain conf.it would be nice to have the following:
--renew
and--renewAll
recognise the--days
parameter--days
value is different from what is stored in the domain conf recalculate theLe_NextRenewTime
andLe_NextRenewTimeStr
valuesThe text was updated successfully, but these errors were encountered: