cURL error 35. Are our IPs blocked?

Help
1

Hello!

We are experiencing problems issuing certificates on two Plesk servers. Same error. Many users with this error found that their IP addresses were blocked by LE. Is it possible to check ours?

My domain is: belek.info
I ran this command: Plesk LetsEncrypt plugin

It produced this output:

Could not obtain directory: cURL error 35: Recv failure: Connection was reset (see libcurl - Error Codes) for https://acme-v02.api.letsencrypt.org/directory

My web server is (include version): IIS 8.5.9600.16384 / IIS 10.0.20348.1.
The operating system my web server runs on is (include version): Windows Server 2022
I can login to a root shell on my machine (yes or no, or I don't know): Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Plesk Obsidian
Version 18.0.63 Update #4

IP: * 141.98.204.178, 141.98.204.170

The output of openssl s_client -connect acme-v02.api.letsencrypt.org:443:

2

Welcome @byfurkany

Actually, most users who suspected they were blocked never were. And, LE does not have any current such blocks.

This is more likely a network routing problem on your end.

Would you show output of these

tracert acme-v02.api.letsencrypt.org
curl https://google.com
curl https://www.cloudflare.com/cdn-cgi/trace
5 Likes
3

host 141.98.204.178 - 178.204.98.141.in-addr.arpa domain name pointer mes03.mescomedia.com.
host 170.204.98.141.in-addr.arpa domain name pointer mes04.mescomedia.com.
So there are more than one IP being validated here..
;@)
I may be blind but...
Both sites open for me.
I so don't understand Plesk....

2 Likes
4

The error was on their outbound connection to
https://acme-v02.api.letsencrypt.org/directory

Not on any inbound connection

3 Likes
5

You're not blind... just looking in the wrong direction!
lol

2 Likes
6

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