# I think my server IP is blocked

**URL:** <https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419>\
**Category:** Help\
**Created:** [July 7, 2023, 1:45pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419 "2023-07-07T13:45:56Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![rconroy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rconroy/32/71824_2.png) [@rconroy](https://community.letsencrypt.org/u/rconroy)\
**Post date:** [July 7, 2023, 1:45pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/1 "2023-07-07T13:45:56Z")

</div>

I run a basic Bash shell that i use to help with my hosting support role. I set up Certbot for generating SSL certs, but it is no longer connecting to [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)

curl: (7) Failed to connect to [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org) port 443: Connection timed out

my server ip is 66.84.14.220, has it been blocked? And if so, can i get the reason so I can investigate

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [July 7, 2023, 1:56pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/2 "2023-07-07T13:56:51Z")

</div>

A connection timeout does not sound like any block from Let's Encrypt. I'm not sure _what_ the error message would be if your IP address was blocked, but I'm preeeetty sure it's not a timeout. It helps debugging while Certbot is paused with the challenge(s) in place.

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [July 7, 2023, 2:09pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/3 "2023-07-07T14:09:46Z")

</div>

Can you connect to anything? Try

```plaintext
curl -I https://google.com

```

---

<div class="post-metadata">

**Author:** ![rconroy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rconroy/32/71824_2.png) [@rconroy](https://community.letsencrypt.org/u/rconroy)\
**Post date:** [July 7, 2023, 4:16pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/4 "2023-07-07T16:16:04Z")

</div>

no issues connecting to any other hosts

unable to ping host  
traceroute ends at cloudflare owned IP

172.69.206.2

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [July 7, 2023, 4:45pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/5 "2023-07-07T16:45:47Z")

</div>

For a traceroute to succeed you'd need to use e.g. the command:

```
sudo traceroute -T -p 443 acme-v02.api.letsencrypt.org

```

Otherwise it'll indeed end at the hop just before the destination. When I do a regular traceroute without any options, the last hop seen is hop nr 5. But with the above command, the traceroute doesn't show anything for hops 1 through 5, but hop 6 is suddenly the final destination and succeeds.

---

<div class="post-metadata">

**Author:** ![rconroy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rconroy/32/71824_2.png) [@rconroy](https://community.letsencrypt.org/u/rconroy)\
**Post date:** [July 7, 2023, 6:41pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/6 "2023-07-07T18:41:39Z")

</div>

it ends in at the same IP

1 [s6.n8.n84.n66.static.myhostcenter.net](http://s6.n8.n84.n66.static.myhostcenter.net) (66.84.8.6) 0.097 ms 0.120 ms 0.047 ms  
2 [23-95-129-9-host.colocrossing.com](http://23-95-129-9-host.colocrossing.com) (23.95.129.9) 0.917 ms 0.824 ms 0.917 ms  
3 [192-210-220-217-host.colocrossing.com](http://192-210-220-217-host.colocrossing.com) (192.210.220.217) 0.919 ms 0.859 ms 1.032 ms  
4 \* 10.8.7.53 (10.8.7.53) 0.495 ms \*  
5 10.8.32.57 (10.8.32.57) 13.303 ms 10.8.5.217 (10.8.5.217) 0.546 ms 10.8.13.233 (10.8.13.233) 0.621 ms  
6 \* \* \*  
7 [be2617.rcr21.yhm01.atlas.cogentco.com](http://be2617.rcr21.yhm01.atlas.cogentco.com) (154.54.0.89) 2.052 ms 2.063 ms 1.986 ms  
8 [be2621.ccr31.yyz02.atlas.cogentco.com](http://be2621.ccr31.yyz02.atlas.cogentco.com) (154.54.40.77) 3.200 ms 3.365 ms 3.323 ms  
9 38.88.240.186 (38.88.240.186) 14.303 ms 14.126 ms 13.981 ms  
10 108.162.239.2 (108.162.239.2) 14.021 ms 13.919 ms 172.69.206.2 (172.69.206.2) 16.469 ms  
11 \* \* \*  
12 \* \* \*  
13 \* \* \*  
14 \* \* \*  
15 \* \* \*  
16 \* \* \*  
17 \* \* \*  
18 \* \* \*  
19 \* \* \*  
20 \* \* \*  
21 \* \* \*  
22 \* \* \*  
23 \* \* \*  
24 \* \* \*  
25 \* \* \*  
26 \* \* \*  
27 \* \* \*  
28 \* \* \*  
29 \* \* \*  
30 \* \* \*

---

<div class="post-metadata">

**Author:** ![rconroy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rconroy/32/71824_2.png) [@rconroy](https://community.letsencrypt.org/u/rconroy)\
**Post date:** [July 7, 2023, 7:07pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/7 "2023-07-07T19:07:25Z")

</div>

this is the command that i use:

sudo certbot --manual --preferred-challenges dns certonly -d \*.$domain -d $domain

same command works on a local machine.

---

<div class="post-metadata">

**Author:** ![jvanasco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jvanasco/32/55900_2.png) [@jvanasco](https://community.letsencrypt.org/u/jvanasco)\
**Post date:** [July 7, 2023, 7:15pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/8 "2023-07-07T19:15:42Z")

</div>

Can you get a response from curl?

```
curl https://acme-v02.api.letsencrypt.org/directory

```

---

<div class="post-metadata">

**Author:** ![rconroy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rconroy/32/71824_2.png) [@rconroy](https://community.letsencrypt.org/u/rconroy)\
**Post date:** [July 10, 2023, 2:50pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/9 "2023-07-10T14:50:27Z")

</div>

curl: (7) Failed to connect to [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org) port 443: Connection timed out

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [July 10, 2023, 4:35pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/10 "2023-07-10T16:35:52Z")

</div>

> [@rconroy](#):
>
> my server ip is 66.84.14.220

Please confirm with:  
`curl ifconfig.io`

---

<div class="post-metadata">

**Author:** ![rconroy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rconroy/32/71824_2.png) [@rconroy](https://community.letsencrypt.org/u/rconroy)\
**Post date:** [July 10, 2023, 6:29pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/11 "2023-07-10T18:29:55Z")

</div>

[rconroy]:~ curl [ifconfig.io](http://ifconfig.io)  
66.84.14.220

---

<div class="post-metadata">

**Author:** ![mcpherrinm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mcpherrinm/32/59604_2.png) [@mcpherrinm](https://community.letsencrypt.org/u/mcpherrinm)\
**Post date:** [July 10, 2023, 6:55pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/12 "2023-07-10T18:55:21Z")

</div>

66.84.14.220 is not blocked.

---

<div class="post-metadata">

**Author:** ![rconroy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rconroy/32/71824_2.png) [@rconroy](https://community.letsencrypt.org/u/rconroy)\
**Post date:** [July 10, 2023, 6:59pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/13 "2023-07-10T18:59:38Z")

</div>

Okay, thanks for checking  
Back to the drawing board 🙃

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [August 9, 2023, 7:00pm UTC](https://community.letsencrypt.org/t/i-think-my-server-ip-is-blocked/201419/14 "2023-08-09T19:00:06Z")

</div>

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