# Could not obtain directory: cURL error 35 and 56: TCP connection reset by peer **URL:** \ **Category:** Help\ **Created:** [November 27, 2022, 10:58am UTC](https://community.letsencrypt.org/t/could-not-obtain-directory-curl-error-35-and-56-tcp-connection-reset-by-peer/188514 "2022-11-27T10:58:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![cloudcanyon](https://avatars.discourse-cdn.com/v4/letter/c/b9bd4f/32.png) [@cloudcanyon](https://community.letsencrypt.org/u/cloudcanyon)\ **Post date:** [November 27, 2022, 10:58am UTC](https://community.letsencrypt.org/t/could-not-obtain-directory-curl-error-35-and-56-tcp-connection-reset-by-peer/188514/1 "2022-11-27T10:58:19Z")
I am using the integrated letsencrypt within Plesk (CentOS 7.9.2009) but since a few days I keep receiving a cURL error 56 followed by 35 after a few requests which leaves me to thing that my server IP has been banned. Where can I request a whitelist? With thanks, ---
**Author:** ![JamesLE](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jamesle/32/49364_2.png) [@JamesLE](https://community.letsencrypt.org/u/JamesLE)\ **Post date:** [November 27, 2022, 11:15am UTC](https://community.letsencrypt.org/t/could-not-obtain-directory-curl-error-35-and-56-tcp-connection-reset-by-peer/188514/2 "2022-11-27T11:15:54Z")
We haven’t added any IP blocks during that timeframe. ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [December 1, 2022, 1:04pm UTC](https://community.letsencrypt.org/t/could-not-obtain-directory-curl-error-35-and-56-tcp-connection-reset-by-peer/188514/3 "2022-12-01T13:04:01Z")
A post was split to a new topic: [cURL error with Plesk on CentOS](https://community.letsencrypt.org/t/curl-error-with-plesk-on-centos/188790) ---
**Author:** ![shimikano](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/shimikano/32/66215_2.png) [@shimikano](https://community.letsencrypt.org/u/shimikano)\ **Post date:** [December 6, 2022, 8:42am UTC](https://community.letsencrypt.org/t/could-not-obtain-directory-curl-error-35-and-56-tcp-connection-reset-by-peer/188514/4 "2022-12-06T08:42:29Z")
I am witnessing a similar behavior using the acme.sh script (latest version 3.0.5) on Arch Linux. Apparently, in a non-deterministic way, but for the majority of requests, curl fails with exit code 35 or 56. Among the affected URLs are: - [https://acme-v02.api.letsencrypt.org/acme/new-order](https://acme-v02.api.letsencrypt.org/acme/new-order) - [https://acme-v02.api.letsencrypt.org/acme/authz-v3/xxx](https://acme-v02.api.letsencrypt.org/acme/authz-v3/xxx) - [https://acme-v02.api.letsencrypt.org/acme/new-nonce](https://acme-v02.api.letsencrypt.org/acme/new-nonce) I am experiencing the same behavior on a different machine (Ubuntu) at a different physical location, which leads me to think that the problem may not be local 🤔 Does anyone have a hint? Thank you. ---
**Author:** ![shimikano](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/shimikano/32/66215_2.png) [@shimikano](https://community.letsencrypt.org/u/shimikano)\ **Post date:** [December 19, 2022, 8:32am UTC](https://community.letsencrypt.org/t/could-not-obtain-directory-curl-error-35-and-56-tcp-connection-reset-by-peer/188514/5 "2022-12-19T08:32:41Z")
For the record, everything started to work again after a few days without me changing any configuration... 🤷 🙂 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [January 18, 2023, 8:33am UTC](https://community.letsencrypt.org/t/could-not-obtain-directory-curl-error-35-and-56-tcp-connection-reset-by-peer/188514/6 "2023-01-18T08:33:16Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.