Originally created by @bjacke on GitHub (Oct 8, 2020).
If you issue a new cert, then the ocsp information for that certificate is sometimes not yet available at the ocsp servers. In such situations a must-staple certificat will be unusable. A small delay between the certificate issuing and the ocsp fetching would help already but it looks like this is not possible to do just by changing the configuration or hook script. A "oscp-fetch-delay-after-cert-issuing" variable is needed I think, a fixed delay of something like 5s might also be okay, but I can imagine that some CAs might need an even longer sleep here.
Originally created by @bjacke on GitHub (Oct 8, 2020).
If you issue a new cert, then the ocsp information for that certificate is sometimes not yet available at the ocsp servers. In such situations a must-staple certificat will be unusable. A small delay between the certificate issuing and the ocsp fetching would help already but it looks like this is not possible to do just by changing the configuration or hook script. A "oscp-fetch-delay-after-cert-issuing" variable is needed I think, a fixed delay of something like 5s might also be okay, but I can imagine that some CAs might need an even longer sleep here.
Workaround for now: Add a delay to your deploy_cert hook.
I'll try to work on a better solution than a simple sleep (which may extremely slow down operation for some users) for the next release.
@lukas2511 commented on GitHub (Dec 10, 2020):
Workaround for now: Add a delay to your `deploy_cert` hook.
I'll try to work on a better solution than a simple sleep (which may extremely slow down operation for some users) for the next release.
FYI, some message related to OCSP delay, from ZeroSSL customer support (2021-01)
Our internal team is confirming that we’re working on improving the speed of the availability for OCSP responses for new certificates - currently OCSP responses are available on average about 1 minute after a certificate was issued. We’re working on improving this time frame drastically.
@zhangyoufu commented on GitHub (Jun 9, 2021):
FYI, some message related to OCSP delay, from ZeroSSL customer support (2021-01)
> Our internal team is confirming that we’re working on improving the speed of the availability for OCSP responses for new certificates - currently OCSP responses are available on average about 1 minute after a certificate was issued. We’re working on improving this time frame drastically.
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 (Oct 8, 2020).
If you issue a new cert, then the ocsp information for that certificate is sometimes not yet available at the ocsp servers. In such situations a must-staple certificat will be unusable. A small delay between the certificate issuing and the ocsp fetching would help already but it looks like this is not possible to do just by changing the configuration or hook script. A "oscp-fetch-delay-after-cert-issuing" variable is needed I think, a fixed delay of something like 5s might also be okay, but I can imagine that some CAs might need an even longer sleep here.
@lukas2511 commented on GitHub (Dec 10, 2020):
Workaround for now: Add a delay to your
deploy_certhook.I'll try to work on a better solution than a simple sleep (which may extremely slow down operation for some users) for the next release.
@zhangyoufu commented on GitHub (Jun 9, 2021):
FYI, some message related to OCSP delay, from ZeroSSL customer support (2021-01)