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
{{ message }}
This repository has been archived by the owner on Dec 1, 2018. It is now read-only.
For various reasons, it can be positive to keep the previous certificates while generating new ones.
For exemple, the new ones could be invalid or buggy, or one want to use DANE, thus needing to wait for DNS propagation.
Currently, letskencrypt store certs at standard place and erase them when generating new ones. There should at least be an option to keep them when creating the new ones.
The text was updated successfully, but these errors were encountered:
For various reasons, it can be positive to keep the previous certificates while generating new ones.
For exemple, the new ones could be invalid or buggy, or one want to use DANE, thus needing to wait for DNS propagation.
Currently, letskencrypt store certs at standard place and erase them when generating new ones. There should at least be an option to keep them when creating the new ones.
The text was updated successfully, but these errors were encountered: