Issue LetsEncrypt: Could not obtain directory: cURL error 35 and 56: TCP connection reset by peer

[Rowan]

Server operating system version

CentOS 7.9.2009

Plesk version and microupdate number

18.0.48

Since a few weeks I cannot renew certificates via the control panel, I continuesly receive a cURL error 35 followed by a cURL error 56 eventually. Automatic renewals seem to do fine.

Similair issues with Plesk are described on the letsencrypt forums:

Could not obtain directory: cURL error 35 and 56: TCP connection reset by peer

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,

community.letsencrypt.org

cURL error with Plesk on CentOS 7.9.2009

Hi @ges, and welcome to the LE community forum Please provide your IP. And any logs that may show us more details on this issue.

community.letsencrypt.org

 

[Peter Debik]

Can you reach Let's Encrypt servers from the console, e.g.

# curl -v https://acme-v02.api.letsencrypt.org
# traceroute -T -p 443 acme-v02.api.letsencrypt.org

?

 

[Rowan]

both commands give a positive response. renewing the certificate also fails from the console. Strangest is that all my other websites renew properly automated, but once I request them manually they fail.

 

[Peter Debik]

When you can connect and renewal still fails with a cURL error, is the cURL error message the only information you get? Or is there maybe another text before or after that explains more? Can you post an example of the console renewal attempt?