Closed bjacke closed 3 years ago
currently letsencrypt has an issue to deliver the correct oscp response after a certificate was issued. dehydrated returns in such cases:
if you run dehydrated after that again it does not see, that the ocsp resonse is invalid and should be updated:
It shoud see that the ocsp response does not match the current certificate and try to fetch a valid resonse instead.
sorry, it turned out that this was a haproxy ocsp problem here, dehydrated is actually doing everything right here and checks that the ocsp response is the right one.
currently letsencrypt has an issue to deliver the correct oscp response after a certificate was issued. dehydrated returns in such cases:
if you run dehydrated after that again it does not see, that the ocsp resonse is invalid and should be updated:
It shoud see that the ocsp response does not match the current certificate and try to fetch a valid resonse instead.