# Get https://acme-staging-v02.api.letsencrypt.org/directory: dial tcp: i/o timeout - kubernetes cert-manager

**URL:** <https://community.letsencrypt.org/t/get-https-acme-staging-v02-api-letsencrypt-org-directory-dial-tcp-i-o-timeout-kubernetes-cert-manager/98766>\
**Category:** Help\
**Created:** [July 30, 2019, 4:13am UTC](https://community.letsencrypt.org/t/get-https-acme-staging-v02-api-letsencrypt-org-directory-dial-tcp-i-o-timeout-kubernetes-cert-manager/98766 "2019-07-30T04:13:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [July 31, 2019, 2:25am UTC](https://community.letsencrypt.org/t/get-https-acme-staging-v02-api-letsencrypt-org-directory-dial-tcp-i-o-timeout-kubernetes-cert-manager/98766/4 "2019-07-31T02:25:39Z")

</div>

Hi @mariesheilag,

I don't know whether this is related to your problem, but cert-manager versions have serious bugs in their Let's Encrypt integration—so serious that Let's Encrypt is planning to block everything prior to 0.8.0 this autumn.

> [@Blocking old cert-manager versions](https://community.letsencrypt.org/t/blocking-old-cert-manager-versions/98753):
>
> W…

Since this blocking hasn't been implemented yet, it's not itself the reason for the error message that you're seeing, but this is an important indication that your cert-manager should be updated to a newer version.

---

_[View the full topic](https://community.letsencrypt.org/t/get-https-acme-staging-v02-api-letsencrypt-org-directory-dial-tcp-i-o-timeout-kubernetes-cert-manager/98766)._