mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-13 15:13:33 +01:00
dehydrated will not replace staging CA certs with real certs, after staging CA removed from config #365
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dave559 on GitHub (Jul 27, 2018).
As part of the (scripted) process of setting up my webserver, I try to request LE certs using the staging CA, and only then try to request certs with the live CA if this is successful (in order to try to prevent any configuration mistakes from triggering rate limits).
I am using dehydrated 0.3.1 (as that's what comes with my distro) and therefore ACME v1.
Once I have my dehydrated configuration setup, I run
dehydrated -c, and then once again after I have commented out the staging CA.However, dehydrated seems to think that my existing cert has not yet expired and so does not renew it.
What would I need to do in order to let dehydrated know that I do genuinely need to request a new cert in this situation?
Thanks for any advice.
@lukas2511 commented on GitHub (Jul 27, 2018):
Dehydrated doesn't refresh your certificate because from its view it's a completely valid certificate.
You can use
--forceto force dehydrated to refresh all certificates.