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
After removing a domain from my list of extraDomains the acme service or that certificate still tried to renew the validation for the removed domain, which was only left as a SAN in the existing certificate at this point.
This is caused by extraDomains not being part of the calculcated hash that would force a renewal of the certificate.
Steps To Reproduce
Steps to reproduce the behavior:
Request a certificate with an extraDomain
Drop the extraDomain
Renew and see how it still tries to renew the removed extraDomain
Expected behavior
Consider removed extraDomain entries for forced renewals.
^ See my comment in the upstream ticket - I feel this would be better fixed in lego itself since surely it is unexpected behaviour. Coincidentally that ticket was opened just 3 days ago 😅
This would work much better than us hacking in a solution (as we already do), and means we can remove domainHash from the module entirely without causing any unwanted force-renewals.
Describe the bug
After removing a domain from my list of extraDomains the acme service or that certificate still tried to renew the validation for the removed domain, which was only left as a SAN in the existing certificate at this point.
This is caused by extraDomains not being part of the calculcated hash that would force a renewal of the certificate.
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
Consider removed extraDomain entries for forced renewals.
Screenshots
n/a
Additional context
n/a
Notify maintainers
@m1cr0man
Metadata
Maintainer information:
The text was updated successfully, but these errors were encountered: