cURL error 35. Are our IPs blocked?

Help
21

If you can reach the server [by any means] on port 443, then your IP is NOT being blocked.

Yes, that is a logical conclusion.
There is no need to "check" it.

3 Likes
22

What about the same case? Nobody asked there if TS could reach the server. But the error was exactly the same.

23

Do you NOT understand how you showed proof that your IP is NOT being blocked?

with:

Unless...
OpenSSL is being NAT hiden with a different IP than the cURL requests!
OR
Somehow one or the other is using a proxy???

3 Likes
24

I do not know how LE IP blocking works. Maybe if I'm blocked, I can reach the server, but can't issue a certificate.

25

No.
Blocked IPs can't get anything at all.
Totally blocked.

3 Likes
26

No, there's no NAT.
Direct routable public IP.

27

What shows?
curl -4 ifconfig.io
curl -6 ifconfig.io

2 Likes
28

image

29

IPv6 is not used.
image

30

Is that the expected IPv4 address?

2 Likes
31

Yes, it's configured on the server's network adapter.

32

Please show:
curl -Ii https://acme-v02.api.letsencrypt.org/directory
curl -Ii https://le-acme-v02.beer4.work/directory

2 Likes
33

image

34

That is bizzare!

What shows?:
traceroute -T -p 443 acme-v02.api.letsencrypt.org

That may not work in Windows... :frowning:

1 Like
35

Yes, it has not "port" option
image

36

I'm lost.
If that IP was blocked, neither PING nor TRACERT would work.

2 Likes
37

I can't agree with this. The IP 172.65.32.248 is owned by Cloudflare. It would be strange if they blocked ICMP to their addresses at the request of one of their tenants.

38

Yes, it is "owned" by Cloudlfare.
But, it is "operated" by LE.
LE is the one doing the blocking.

2 Likes
39

keep mind that error is when try to access auth url: if IP was blocked it wouldn't able to create that URL by asking a order that would create it

3 Likes
40

Ok. What's this?
image