# What if Let's Encrypt goes down? - OCSP Stapling

**URL:** <https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369>\
**Category:** Help\
**Created:** [November 8, 2016, 11:12pm UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369 "2016-11-08T23:12:25Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neutralizer](https://avatars.discourse-cdn.com/v4/letter/n/e19adc/32.png) [@Neutralizer](https://community.letsencrypt.org/u/Neutralizer)\
**Post date:** [November 8, 2016, 11:12pm UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/1 "2016-11-08T23:12:25Z")

</div>

Hello Everyone, 🙂

I’ve enabled Online Certificate Status Protocol (OCSP) stapling on my servers and I would like to know what happens when lets encrypt goes down?

I know that SSL will still function but **since I have OCSP stapling enabled, it won’t be able to connect to Let’s Encrypt servers to verify my SSL**.

Please share your thoughts / experiences

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [November 8, 2016, 11:53pm UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/2 "2016-11-08T23:53:08Z")

</div>

@Neutralizer, I believe you have it backwards here, at least if you’re talking about a user’s experience visiting your site: OCSP stapling means that the OCSP response data is _sent by your server along with the certificate_, so that a visitor’s browser _doesn’t_ have to query the Let’s Encrypt OCSP servers to check that your certificate is still valid. In this regard, OCSP stapling should make your site’s availability better, not worse, in case of a Let’s Encrypt outage.

---

<div class="post-metadata">

**Author:** ![Svavar\_Kjarrval](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@Svavar\_Kjarrval](https://community.letsencrypt.org/u/Svavar_Kjarrval)\
**Post date:** [November 9, 2016, 9:55am UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/4 "2016-11-09T09:55:55Z")

</div>

> [@schoen](#):
>
> In this regard, OCSP stapling should make your site's availability better, not worse, in case of a Let's Encrypt outage.

Unless the web server seeks the OCSP response when the LE OCSP servers are down. It happened once when all the LE OCSP servers suddenly went into maintenence. Some of the domains had no valid OCSP responses with the certificates and FireFox deemed them invalid for the rest of the maintenence.

---

<div class="post-metadata">

**Author:** ![tialaramex](https://avatars.discourse-cdn.com/v4/letter/t/f08c70/32.png) [@tialaramex](https://community.letsencrypt.org/u/tialaramex)\
**Post date:** [November 9, 2016, 3:27pm UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/5 "2016-11-09T15:27:41Z")

</div>

This is a misfeature in some server software, unfortunately including (at least by default) the Apache httpd.

What a good server _should_ do is remember the last OCSP Good response it has, even when restarted, and provide that until it expires, meanwhile trying periodically to get a fresher Good response.

Ryan Sleevi wrote about this here: [https://gist.github.com/sleevi/5efe9ef98961ecfb4da8](https://gist.github.com/sleevi/5efe9ef98961ecfb4da8)

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [November 9, 2016, 6:53pm UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/6 "2016-11-09T18:53:34Z")

</div>

> [@schoen](#):
>
> In this regard, OCSP stapling should make your site's availability better, not worse, in case of a Let's Encrypt outage.

[Standard revocation checking isn't working](https://www.imperialviolet.org/2014/04/19/revchecking.html), but OCSP Must Staple is a _ **big** _ improvement. Should be the new standard way of revocation checking if you ask me.. But if there's an outage... 😉

---

<div class="post-metadata">

**Author:** ![Armoured](https://avatars.discourse-cdn.com/v4/letter/a/e9c0ed/32.png) [@Armoured](https://community.letsencrypt.org/u/Armoured)\
**Post date:** [November 10, 2016, 8:29am UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/7 "2016-11-10T08:29:07Z")

</div>

@osiris could you please help me with this site registered under letsencrypt as i am having issue with it.thanks

---

<div class="post-metadata">

**Author:** ![Armoured](https://avatars.discourse-cdn.com/v4/letter/a/e9c0ed/32.png) [@Armoured](https://community.letsencrypt.org/u/Armoured)\
**Post date:** [November 10, 2016, 8:30am UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/8 "2016-11-10T08:30:14Z")

</div>

Taskmine.club that’s it

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [November 10, 2016, 11:01am UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/9 "2016-11-10T11:01:51Z")

</div>

For help with a specific problem, not related to this thread, you should start a new thread, including answering the question template when presented.

---

<div class="post-metadata">

**Author:** ![Armoured](https://avatars.discourse-cdn.com/v4/letter/a/e9c0ed/32.png) [@Armoured](https://community.letsencrypt.org/u/Armoured)\
**Post date:** [November 11, 2016, 7:40am UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/10 "2016-11-11T07:40:39Z")

</div>

Thank you very much am very grateful

---

<div class="post-metadata">

**Author:** ![BFeely](https://avatars.discourse-cdn.com/v4/letter/b/c37758/32.png) [@BFeely](https://community.letsencrypt.org/u/BFeely)\
**Post date:** [November 11, 2016, 11:31am UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/11 "2016-11-11T11:31:25Z")

</div>

That would tell me that CAs should ensure their OCSP infrastructure has redundancy and that maintenance never happens on all machines at once.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [December 11, 2016, 11:31am UTC](https://community.letsencrypt.org/t/what-if-lets-encrypt-goes-down-ocsp-stapling/22369/12 "2016-12-11T11:31:26Z")

</div>

Closed on December 11, 2016, 11:31am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
