# Possibly blocked IP address

**URL:** <https://community.letsencrypt.org/t/possibly-blocked-ip-address/198611>\
**Category:** Help\
**Created:** [May 18, 2023, 9:47pm UTC](https://community.letsencrypt.org/t/possibly-blocked-ip-address/198611 "2023-05-18T21:47:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![networldweb](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/networldweb/32/70531_2.png) [@networldweb](https://community.letsencrypt.org/u/networldweb)\
**Post date:** [May 18, 2023, 9:47pm UTC](https://community.letsencrypt.org/t/possibly-blocked-ip-address/198611/1 "2023-05-18T21:47:10Z")

</div>

Hello!  
I believe that my server's IP address may be blocked. It's been a while since my server can't connect to the Let's Encrypt server.  
It is showing the following error message:

# curl -v [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory)

- Trying 172.65.32.248...
- TCP\_NODELAY set
- Connected to [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org) (172.65.32.248) port 443 (#0)
- ALPN, offering h2
- ALPN, offering http/1.1
- successfully set certificate verify locations:
- CAfile: /etc/pki/tls/certs/ca-bundle.crt  
CApath: none
- TLSv1.3 (OUT), TLS handshake, Client hello (1):
- TLSv1.3 (IN), TLS handshake, Server hello (2):
- TLSv1.3 (IN), TLS handshake, [no content] (0):
- TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
- TLSv1.3 (IN), TLS handshake, [no content] (0):
- TLSv1.3 (IN), TLS handshake, Certificate (11):
- TLSv1.3 (IN), TLS handshake, [no content] (0):
- TLSv1.3 (IN), TLS handshake, CERT verify (15):
- TLSv1.3 (IN), TLS handshake, [no content] (0):
- TLSv1.3 (IN), TLS handshake, Finished (20):
- TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
- TLSv1.3 (OUT), TLS handshake, [no content] (0):
- TLSv1.3 (OUT), TLS handshake, Finished (20):
- SSL connection using TLSv1.3 / TLS\_AES\_256\_GCM\_SHA384
- ALPN, server accepted to use h2
- Server certificate:
- subject: [CN=acme-v02.api.letsencrypt.org](http://CN=acme-v02.api.letsencrypt.org)
- start date: May 1 18:14:19 2023 GMT
- expire date: Jul 30 18:14:18 2023 GMT
- subjectAltName: host "[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)" matched cert's "[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)"
- issuer: C=US; O=Let's Encrypt; CN=R3
- SSL certificate verify ok.
- Using HTTP2, server supports multi-use
- Connection state changed (HTTP/2 confirmed)
- Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
- TLSv1.3 (OUT), TLS app data, [no content] (0):
- TLSv1.3 (OUT), TLS app data, [no content] (0):
- TLSv1.3 (OUT), TLS app data, [no content] (0):
- Using Stream ID: 1 (easy handle 0x5592ff0046b0)
- TLSv1.3 (OUT), TLS app data, [no content] (0):

> GET /directory HTTP/2  
> Host: [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)  
> User-Agent: curl/7.61.1  
> Accept: _/_

- TLSv1.3 (IN), TLS handshake, [no content] (0):
- TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
- TLSv1.3 (IN), TLS handshake, [no content] (0):
- TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
- TLSv1.3 (IN), TLS app data, [no content] (0):
- Connection state changed (MAX\_CONCURRENT\_STREAMS == 128)!
- TLSv1.3 (OUT), TLS app data, [no content] (0):
- TLSv1.3 (IN), TLS app data, [no content] (0):
- TLSv1.3 (IN), TLS app data, [no content] (0):  
\< HTTP/2 200  
\< server: nginx  
\< date: Thu, 18 May 2023 21:24:08 GMT  
\< content-type: application/json  
\< content-length: 752  
\< cache-control: public, max-age=0, no-cache  
\< x-frame-options: DENY  
\< strict-transport-security: max-age=604800  
\<  
{  
"Z8h7V2idJVY": "[Adding random entries to the directory](https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417)",  
"keyChange": "[https://acme-v02.api.letsencrypt.org/acme/key-change](https://acme-v02.api.letsencrypt.org/acme/key-change)",  
"meta": {  
"caaIdentities": [  
"[letsencrypt.org](http://letsencrypt.org)"  
],  
"termsOfService": "[https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf](https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf)",  
"website": "[https://letsencrypt.org](https://letsencrypt.org)"  
},  
"newAccount": "[https://acme-v02.api.letsencrypt.org/acme/new-acct](https://acme-v02.api.letsencrypt.org/acme/new-acct)",  
"newNonce": "[https://acme-v02.api.letsencrypt.org/acme/new-nonce](https://acme-v02.api.letsencrypt.org/acme/new-nonce)",  
"newOrder": "[https://acme-v02.api.letsencrypt.org/acme/new-order](https://acme-v02.api.letsencrypt.org/acme/new-order)",  
"renewalInfo": "[https://acme-v02.api.letsencrypt.org/draft-ietf-acme-ari-01/renewalInfo/](https://acme-v02.api.letsencrypt.org/draft-ietf-acme-ari-01/renewalInfo/)",  
"revokeCert": "[https://acme-v02.api.letsencrypt.org/acme/revoke-cert](https://acme-v02.api.letsencrypt.org/acme/revoke-cert)"
- Connection #0 to host [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org) left intact

Estou fazendo esse teste acima, via comando shell, "CloudLinux 8.7".

When I try to activate Let's Encrypt through cPanel "WHM", I get the following error:

API failure: Net::ACME2:❌:HTTP::Network: The system failed to send an HTTP “GET” request to “[https://acme-v02.api.letsencrypt.org/directory”](https://acme-v02.api.letsencrypt.org/directory%E2%80%9D) because of an error: SSL connection failed for [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org): SSL connect attempt failed error:1416F086:SSL routines:tls\_process\_server\_certificate:certificate verify failed ...propagated at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Net/ACME2/HTTP.pm, line 225

Remembering that it was working normally, but it has about 20 days that it stopped working.

If anyone can help!

Thank you!

---

<div class="post-metadata">

**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\
**Post date:** [May 18, 2023, 10:01pm UTC](https://community.letsencrypt.org/t/possibly-blocked-ip-address/198611/2 "2023-05-18T22:01:11Z")

</div>

> [@networldweb](#):
>
> It is showing the following error message:

That error message makes it clear that you can connect to the Let's Encrypt server. Whatever the problem is, it isn't that your IP is blocked (and that's almost never the problem).

---

<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:** [May 18, 2023, 10:03pm UTC](https://community.letsencrypt.org/t/possibly-blocked-ip-address/198611/3 "2023-05-18T22:03:28Z")

</div>

> [@networldweb](#):
>
> certificate verify failed

This could be due to some misconfiguration of the client, like configuring a nonstandard trust store meant for some internal use.

The curl command shows you aren't blocked and your system generally trusts Let's Encrypt.

---

<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:** [May 18, 2023, 10:04pm UTC](https://community.letsencrypt.org/t/possibly-blocked-ip-address/198611/4 "2023-05-18T22:04:34Z")

</div>

> [@networldweb](#):
>
> `certificate verify failed`

Try obtaining a cert from another free CA.

---

<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:** [June 17, 2023, 10:05pm UTC](https://community.letsencrypt.org/t/possibly-blocked-ip-address/198611/5 "2023-06-17T22:05:19Z")

</div>

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