How can I check is my IP blocked or not?

I'm using built in generator in a ISP6. IP 91.210.171.213
error in log: Type: 'rpc' Object: 'query' Value: 'query: SSL connect error'
url: https://acme-v02.api.letsencrypt.org/acme/acct/354109220

My domain is: kriptoplan.ru

I try do
wget https://acme-v02.api.letsencrypt.org/acme/acct/354109220

from server - I get:
Resolving acme-v02.api.letsencrypt.org (acme-v02.api.letsencrypt.org)... 172.65.32.248, 2606:4700:60:0:f53d:5624:85c7:3a2c
Connecting to acme-v02.api.letsencrypt.org (acme-v02.api.letsencrypt.org)|172.65.32.248|:443... connected.
GnuTLS: Error in the pull function.
Unable to establish SSL connection.

Usually the client would report a "handshake error" if there is a problem with blocks due to DDoS prevention. However, I'm not sure how GnuTLS would report such a thing.

Let's just ask the professionals at @lestaff :slight_smile:

3 Likes

Hi, @dellmaster,

We're not blocking or rate limiting your IP addresses, but your report looks like it's related to this problem that we're investigating: API service disruption for Russian subscribers

4 Likes

Hi, @dellmaster,

Could you please show us the output of a traceroute to acme-v02.api.letsencrypt.org? Feel free to either post it here or send it to me as a direct message.

4 Likes

Hi, @JamesLE
(Russian server)

traceroute acme-v02.api.letsencrypt.org

traceroute to acme-v02.api.letsencrypt.org (172.65.32.248), 30 hops max, 60 byte packets
1 185.4.67.253 (185.4.67.253) 1.005 ms 1.029 ms 1.219 ms
2 195.209.62.67 (195.209.62.67) 0.486 ms J1-SLV-MG1.net.reconn.ru (195.209.63.101) 0.499 ms 195.209.62.7
7 (195.209.62.77) 0.487 ms
3 109.239.135.58 (109.239.135.58) 0.892 ms 31.28.19.100 (31.28.19.100) 0.501 ms 6.203 ms
4 10.10.13.153 (10.10.13.153) 18.058 ms 18.065 ms 7.829 ms
5 109.239.136.210 (109.239.136.210) 7.447 ms 7.427 ms spx-ix.as13335.net (194.226.100.129) 8.554 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

2 Likes

traceroute to acme-v02.api.letsencrypt.org (172.65.32.248), 30 hops max, 60 byte packets
1 vds-cp76619.timeweb.ru (2.59.40.1) 0.947 ms 0.976 ms 0.962 ms
2 172.17.1.1 (172.17.1.1) 12.009 ms 12.182 ms 12.186 ms
3 spx-ix.as13335.net (194.226.100.129) 1.475 ms 1.394 ms 1.436 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

1 Like

We believe the network routing problem from the St. Petersburg, Russia region is now resolved. If you're still having trouble, please let us know. Thanks for your patience!

3 Likes

thank you!

2 Likes

Hi, troble still exists.
traceroute to acme-v02.api.letsencrypt.org (172.65.32.248), 30 hops max, 60 byte packets
1 77-222-55-253.vps-ptr.clients.spaceweb.ru (77.222.55.253) 16.571 ms 16.542 ms 16.592 ms
2 spb-sdn-nr1.nic.ru (31.177.85.164) 0.940 ms 3.051 ms 3.036 ms
3 213.59.214.153 (213.59.214.153) 8.735 ms 8.721 ms 8.700 ms
4 87.226.181.85 (87.226.181.85) 13.850 ms 87.226.183.85 (87.226.183.85) 13.000 ms *
5 95.71.2.226 (95.71.2.226) 14.029 ms 24.882 ms 65.900 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

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