# Can't access https://acme-v01.api.letsencrypt.org/directory

**URL:** <https://community.letsencrypt.org/t/cant-access-https-acme-v01-api-letsencrypt-org-directory/56872>\
**Category:** Help\
**Created:** [March 18, 2018, 4:15pm UTC](https://community.letsencrypt.org/t/cant-access-https-acme-v01-api-letsencrypt-org-directory/56872 "2018-03-18T16:15:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dragomir-Ivanov](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dragomir-ivanov/32/21664_2.png) [@Dragomir-Ivanov](https://community.letsencrypt.org/u/Dragomir-Ivanov)\
**Post date:** [March 18, 2018, 4:15pm UTC](https://community.letsencrypt.org/t/cant-access-https-acme-v01-api-letsencrypt-org-directory/56872/1 "2018-03-18T16:15:13Z")

</div>

Hi,  
It seems I can’t access `https://acme-v01.api.letsencrypt.org/directory` from my domain.  
wget [https://acme-v01.api.letsencrypt.org/directory](https://acme-v01.api.letsencrypt.org/directory)  
times out.

It is accessible from other domain so I guess I am in some blacklist for my cloud provider IP sub-net.  
Domain: [feroko.com](http://feroko.com)  
IP: 23.244.69.133

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [March 18, 2018, 4:43pm UTC](https://community.letsencrypt.org/t/cant-access-https-acme-v01-api-letsencrypt-org-directory/56872/2 "2018-03-18T16:43:43Z")

</div>

Hi,

Can you try `curl https://acme-v02.api.letsencrypt.org/directory` and share the output?

---

<div class="post-metadata">

**Author:** ![Dragomir-Ivanov](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dragomir-ivanov/32/21664_2.png) [@Dragomir-Ivanov](https://community.letsencrypt.org/u/Dragomir-Ivanov)\
**Post date:** [March 18, 2018, 5:15pm UTC](https://community.letsencrypt.org/t/cant-access-https-acme-v01-api-letsencrypt-org-directory/56872/3 "2018-03-18T17:15:15Z")

</div>

Sorry for the false alarm, the issue seems to be that these requests take too much time \> 2minutes. I guess it is some network issue, rather LetsEncrypt. Thanks a lot.

[root@prod1 ~]# time curl [https://acme-v01.api.letsencrypt.org/directory](https://acme-v01.api.letsencrypt.org/directory)  
{  
“B9GMAHh9hjQ”: “[Adding random entries to the directory](https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417)”,  
“key-change”: “[https://acme-v01.api.letsencrypt.org/acme/key-change](https://acme-v01.api.letsencrypt.org/acme/key-change)”,  
“meta”: {  
“terms-of-service”: “[https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf](https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf)”  
},  
“new-authz”: “[https://acme-v01.api.letsencrypt.org/acme/new-authz](https://acme-v01.api.letsencrypt.org/acme/new-authz)”,  
“new-cert”: “[https://acme-v01.api.letsencrypt.org/acme/new-cert](https://acme-v01.api.letsencrypt.org/acme/new-cert)”,  
“new-reg”: “[https://acme-v01.api.letsencrypt.org/acme/new-reg](https://acme-v01.api.letsencrypt.org/acme/new-reg)”,  
“revoke-cert”: “[https://acme-v01.api.letsencrypt.org/acme/revoke-cert](https://acme-v01.api.letsencrypt.org/acme/revoke-cert)”  
}  
real 2m6.353s  
user 0m0.086s  
sys 0m0.082s  
[root@prod1 ~]# time curl [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory)  
{  
“EOHe1tFziCk”: “[Adding random entries to the directory](https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417)”,  
“keyChange”: “[https://acme-v02.api.letsencrypt.org/acme/key-change](https://acme-v02.api.letsencrypt.org/acme/key-change)”,  
“meta”: {  
“termsOfService”: “[https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf](https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf)”  
},  
“newAccount”: “[https://acme-v02.api.letsencrypt.org/acme/new-acct](https://acme-v02.api.letsencrypt.org/acme/new-acct)”,  
“newNonce”: “[https://acme-v02.api.letsencrypt.org/acme/new-nonce](https://acme-v02.api.letsencrypt.org/acme/new-nonce)”,  
“newOrder”: “[https://acme-v02.api.letsencrypt.org/acme/new-order](https://acme-v02.api.letsencrypt.org/acme/new-order)”,  
“revokeCert”: “[https://acme-v02.api.letsencrypt.org/acme/revoke-cert](https://acme-v02.api.letsencrypt.org/acme/revoke-cert)”  
}  
real 2m6.450s  
user 0m0.085s  
sys 0m0.084s

---

<div class="post-metadata">

**Author:** ![Dragomir-Ivanov](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dragomir-ivanov/32/21664_2.png) [@Dragomir-Ivanov](https://community.letsencrypt.org/u/Dragomir-Ivanov)\
**Post date:** [March 18, 2018, 11:31pm UTC](https://community.letsencrypt.org/t/cant-access-https-acme-v01-api-letsencrypt-org-directory/56872/4 "2018-03-18T23:31:50Z")

</div>

Issue was due to some IPv6 network issues. Not related to Lets Encrypt in any way. Thanks all.

---

<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:** [April 17, 2018, 11:32pm UTC](https://community.letsencrypt.org/t/cant-access-https-acme-v01-api-letsencrypt-org-directory/56872/5 "2018-04-17T23:32:04Z")

</div>

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