Problem when recreate my registration - manage ssl cpanel whm

dedowbas · May 4, 2023, 10:30am

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
84.16.241.208
I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):
centos 7
My hosting provider, if applicable, is:
leaseweb
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):
cpanel
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

i got this when pick lets encrypt ssl from manage ssl cpanel whm and save

API failure: Net::ACME2::HTTP::Network: The system failed to send an HTTP “GET” request to “https://acme-v02.api.letsencrypt.org/directory” because of an error: SSL connection failed for acme-v02.api.letsencrypt.org: SSL connect attempt failed error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed ...propagated at /usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/Net/ACME2/HTTP.pm, line 225

Bruce5051 · May 4, 2023, 2:35pm

Hello @dedowbas, welcome to the Let's Encrypt community.

The key here is Doman Name not an IP Address.

Let’s Encrypt offers Domain Validation (DV) certificates.

Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

Thus you need to own and have control over the Domain Name (or have a subdomain under an existing domain name, for example pointed to your server by your employer or school) you wish to obtain a certificate for, from an ICANN Accredited Registrar.

For Let’s Encrypt to issue a Domain Validation (DV) certificate Domain Validation must happen
and it is a CA/Browser Forum Baseline Requirement.

What IP addresses does Let’s Encrypt use to validate my web server?
Let’s Encrypt does not publish a list of IP addresses we use to validate,
and these IP addresses may change at any time.

Let's Encrypt uses Multi-Perspective Validation Improves Domain Validation Security - Let's Encrypt

Since these are Domain Validation (DV) certificates the Domain Name System (DNS) is used extensively in the validation process as well a allowing us to assist here on Let's Encrypt community.
DNS Queries need to give consistent results from any location on the Internet, all your authoritative DNS Servers for the Domain need to also give consistent results as well.

rg305 · May 4, 2023, 4:13pm

Aside from the lack of FQDN...
There seems to be a routing of firewall issue that is preventing your system from reaching LE:

dedowbas · May 4, 2023, 10:07pm

i turn off csf firewall to check but same
can imunfy360 block it

Bruce5051 · May 4, 2023, 10:09pm

What is the Domain Name?

dedowbas · May 4, 2023, 10:11pm

i have problem with my server for all domains

AutoSSL Providers in whm cpanel

it was work before without problem

dedowbas · May 4, 2023, 10:17pm

[root@server ~]# curl -v acme-v02.api.letsencrypt.org

* About to connect() to acme-v02.api.letsencrypt.org port 80 (#0)
*   Trying 172.65.32.248...
* Connected to acme-v02.api.letsencrypt.org (172.65.32.248) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: acme-v02.api.letsencrypt.org
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

Bruce5051 · May 4, 2023, 10:19pm

try curl -v www.google.com; let's see if you can connect out to anything

These are good to check you own IP Address as seen from the Public Internet

curl -4 ifconfig.co
curl -6 ifconfig.co

and/or

curl -4 ifconfig.io
curl -6 ifconfig.io

Bruce5051 · May 4, 2023, 10:28pm

I do find the FQDN of server.ayadytnlfbharir.com has the IPv4 Address of 84.16.241.208

$ nslookup -q=any server.ayadytnlfbharir.com ns1.ayadytnlfbharir.com.
;; Truncated, retrying in TCP mode.
Server:         ns1.ayadytnlfbharir.com.
Address:        84.16.241.208#53

server.ayadytnlfbharir.com      text = "v=spf1 +mx +a +ip4:84.16.241.208 ~all"
server.ayadytnlfbharir.com      mail exchanger = 0 server.ayadytnlfbharir.com.
Name:   server.ayadytnlfbharir.com
Address: 84.16.241.208
server.ayadytnlfbharir.com      nameserver = ns2.ayadytnlfbharir.com.
server.ayadytnlfbharir.com      nameserver = ns1.ayadytnlfbharir.com.
server.ayadytnlfbharir.com
        origin = ns1.ayadytnlfbharir.com
        mail addr = server.ayadytnlfbharir.com
        serial = 2021112201
        refresh = 3600
        retry = 1800
        expire = 1209600
        minimum = 86400

Bruce5051 · May 4, 2023, 10:38pm

And you may have a DNS issue as well server.ayadytnlfbharir.com | DNSViz

And related DNS Spy report for ayadytnlfbharir.com

dedowbas · May 4, 2023, 10:45pm

[root@server ~]# curl -4 ifconfig.io
84.16.241.208

everything fine

Bruce5051 · May 4, 2023, 10:47pm

So you can connect out in general, just not to

Hmm.

Kindly wait to see if there are more knowledgeable Let's Encrypt community volunteers willing to assist.

dedowbas · May 4, 2023, 10:51pm

it stop working suddenly it work more than 2 years

Bruce5051 · May 4, 2023, 11:04pm

Actually I think your curl -v acme-v02.api.letsencrypt.org fine, this is what I get.
(Maybe you had meant to do curl -v https://acme-v02.api.letsencrypt.org
or even better yet curl -v https://acme-v02.api.letsencrypt.org/directory)

$ curl -v acme-v02.api.letsencrypt.org
*   Trying 172.65.32.248:80...
* Connected to acme-v02.api.letsencrypt.org (172.65.32.248) port 80 (#0)
> GET / HTTP/1.1
> Host: acme-v02.api.letsencrypt.org
> User-Agent: curl/7.81.0
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

$ curl -Ii http://acme-v02.api.letsencrypt.org
curl: (52) Empty reply from server

$ curl -Ii https://acme-v02.api.letsencrypt.org
HTTP/2 200
server: nginx
date: Thu, 04 May 2023 23:03:13 GMT
content-type: text/html
content-length: 1540
last-modified: Thu, 23 Jun 2022 21:18:15 GMT
etag: "62b4d897-604"
x-frame-options: DENY
strict-transport-security: max-age=604800

dedowbas · May 4, 2023, 11:18pm

[root@server ~]# curl -v acme-v02.api.letsencrypt.org

* About to connect() to acme-v02.api.letsencrypt.org port 80 (#0)
*   Trying 172.65.32.248...
* Connected to acme-v02.api.letsencrypt.org (172.65.32.248) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: acme-v02.api.letsencrypt.org
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

[root@server ~]# curl -v https://acme-v02.api.letsencrypt.org

* About to connect() to acme-v02.api.letsencrypt.org port 443 (#0)
*   Trying 172.65.32.248...
* Connected to acme-v02.api.letsencrypt.org (172.65.32.248) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject: CN=acme-v02.api.letsencrypt.org
*       start date: May 01 18:14:19 2023 GMT
*       expire date: Jul 30 18:14:18 2023 GMT
*       common name: acme-v02.api.letsencrypt.org
*       issuer: CN=R3,O=Let's Encrypt,C=US
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: acme-v02.api.letsencrypt.org
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx
< Date: Thu, 04 May 2023 23:17:33 GMT
< Content-Type: text/html
< Content-Length: 1540
< Last-Modified: Thu, 23 Jun 2022 21:26:20 GMT
< Connection: keep-alive
< ETag: "62b4da7c-604"
< X-Frame-Options: DENY
< Strict-Transport-Security: max-age=604800
<
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <title>Boulder: The Let's Encrypt CA</title>

  <style type="text/css">
    header { display: flex; max-height: 30vh; flex-wrap: wrap; margin-bottom: 10vh; }
    header img { display: flex; max-height: 20vh; align-content: flex-end; margin-right: 20px; }
  </style>
</head>

<body>
  <header>
    <section>
      <img src="/static/images/LE-Logo-LockOnly.svg"/>
    </section>
    <section>
      <h1>Boulder<br>
      <small>The Let's Encrypt CA</small></h1>
    </section>
  </header>

  <section>
    <p>This is an <a href="https://tools.ietf.org/html/rfc8555">ACME</a> Certificate Authority running <a href="https://github.com/letsencrypt/boulder">Boulder</a>.</p>
    <p>This is a <em>programmatic</em> endpoint, an API for a computer to talk to. You should probably be using a specialized client to utilize the service, and not your web browser. See <a href="https://letsencrypt.org/docs"><tt>https://letsencrypt.org/docs</tt></a>for help.</p>
    <p>If you're trying to use this service, note that the starting point, <em>the directory</em>, is available at this URL: <a href="https://acme-v02.api.letsencrypt.org/directory"><tt>https://acme-v02.api.letsencrypt.org/directory</a></tt>.</p>
  </section>

  <footer>
      <p>
        <a href="https://letsencrypt.status.io" title="Status">Service Status (letsencrypt.status.io)</a> |
        <a href="https://twitter.com/letsencrypt" title="Twitter">Let's Encrypt Twitter</a>
      </p>
  </footer>

</body>
</html>
* Connection #0 to host acme-v02.api.letsencrypt.org left intact