Originally created by @bjacke on GitHub (Dec 3, 2020).
currently letsencrypt has an issue to deliver the correct oscp response after a certificate was issued. dehydrated returns in such cases:
Updating OCSP stapling file
OCSP single response: Certificate ID does not match any certificate or issuer.
if you run dehydrated after that again it does not see, that the ocsp resonse is invalid and should be updated:
OCSP stapling file is still valid (skipping update)
It shoud see that the ocsp response does not match the current certificate and try to fetch a valid resonse instead.
Originally created by @bjacke on GitHub (Dec 3, 2020).
currently letsencrypt has an issue to deliver the correct oscp response after a certificate was issued. dehydrated returns in such cases:
+ Updating OCSP stapling file
OCSP single response: Certificate ID does not match any certificate or issuer.
if you run dehydrated after that again it does not see, that the ocsp resonse is invalid and should be updated:
+ OCSP stapling file is still valid (skipping update)
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.
@bjacke commented on GitHub (Dec 10, 2020):
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @bjacke on GitHub (Dec 3, 2020).
currently letsencrypt has an issue to deliver the correct oscp response after a certificate was issued. dehydrated returns in such cases:
OCSP single response: Certificate ID does not match any certificate or issuer.
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.
@bjacke commented on GitHub (Dec 10, 2020):
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.