# Plesk and could not issue a Let’s Encrypt SSL/TLS due cURL error 56 **URL:** \ **Category:** Help\ **Created:** [March 21, 2022, 10:21am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205 "2022-03-21T10:21:36Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![avklinken](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@avklinken](https://community.letsencrypt.org/u/avklinken)\ **Post date:** [March 21, 2022, 10:21am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205/1 "2022-03-21T10:21:36Z")
Hi I tried to reissue a certificate in plesk and it just errors out with a curl error. It might be our IP is on your blocklist for some reason? The ip is: 145.131.3.230 Edit: sorry its Curl error 56 ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [March 21, 2022, 10:53am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205/2 "2022-03-21T10:53:44Z")
[https://curl.se/libcurl/c/libcurl-errors.html](https://curl.se/libcurl/c/libcurl-errors.html) > CURLE\_SSL\_CONNECT\_ERROR (35) > > A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others. Does your server have `ISRG Root X1` in its keystore? [Certificate Compatibility - Let's Encrypt](https://letsencrypt.org/docs/certificate-compatibility/#platforms-that-trust-isrg-root-x1) Try running `openssl s_client -quiet -verify 10 -connect acme-v02.api.letsencrypt.org:443` ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [March 21, 2022, 10:58am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205/3 "2022-03-21T10:58:48Z")
> [@avklinken](#): > > Edit: sorry its Curl error 56 > CURLE\_RECV\_ERROR (56) > > Failure with receiving network data. Uhm. ---
**Author:** ![avklinken](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@avklinken](https://community.letsencrypt.org/u/avklinken)\ **Post date:** [March 21, 2022, 10:59am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205/4 "2022-03-21T10:59:03Z")
> [@9peppe](#): > > openssl s\_client -quiet -verify 10 -connect [acme-v02.api.letsencrypt.org:443](http://acme-v02.api.letsencrypt.org:443) Thanks. I have made a mistake on the error code. The openssl command returns this: openssl s\_client -quiet -verify 10 -connect [acme-v02.api.letsencrypt.org:443](http://acme-v02.api.letsencrypt.org:443) depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = R3 verify return:1 depth=0 CN = [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org) verify return:1 ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [March 21, 2022, 11:00am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205/5 "2022-03-21T11:00:15Z")
So the certificate is fine and you can connect to the ACME endpoint. Now try: `curl -iL https://acme-v02.api.letsencrypt.org/directory` ---
**Author:** ![avklinken](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@avklinken](https://community.letsencrypt.org/u/avklinken)\ **Post date:** [March 21, 2022, 11:07am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205/6 "2022-03-21T11:07:52Z")
That returns this: HTTP/1.1 200 OK Server: nginx Date: Mon, 21 Mar 2022 11:07:21 GMT Content-Type: application/json Content-Length: 658 Connection: keep-alive Cache-Control: public, max-age=0, no-cache X-Frame-Options: DENY Strict-Transport-Security: max-age=604800 { "A6kIuX1nBIo": "[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": { "caaIdentities": [ "[letsencrypt.org](http://letsencrypt.org)" ], "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)", "website": "[https://letsencrypt.org](https://letsencrypt.org)" }, "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)" ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [March 21, 2022, 11:12am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205/7 "2022-03-21T11:12:26Z")
So the problem is not with your server, nor your network, nor Let's Encrypt: plesk is messing up or something else (a firewall?) is interfering with it. And I don't know plesk. Sorry. I hope somebody else here knows more. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [April 20, 2022, 11:12am UTC](https://community.letsencrypt.org/t/plesk-and-could-not-issue-a-let-s-encrypt-ssl-tls-due-curl-error-56/174205/8 "2022-04-20T11:12:57Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.