Hi sorry for late reply.
Result for curl -4
curl -v4 https://acme-v02.api.letsencrypt.org/directory
- 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_256_GCM_SHA384
- Server certificate:
-
subject: CN=acme-v01.api.letsencrypt.org
-
start date: Mar 12 18:07:07 2020 GMT
-
expire date: Jun 10 18:07:07 2020 GMT
-
common name: acme-v01.api.letsencrypt.org
-
issuer: CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US
GET /directory HTTP/1.1
User-Agent: curl/7.29.0
Host: acme-v02.api.letsencrypt.org
Accept: /
< HTTP/1.1 200 OK
< Server: nginx
< Date: Tue, 14 Apr 2020 09:46:17 GMT
< Content-Type: application/json
< Content-Length: 658
< Connection: keep-alive
< Cache-Control: public, max-age=0, no-cache
< X-Frame-Options: DENY
< Strict-Transport-Security: max-age=604800
<
{
"keyChange": "https://acme-v02.api.letsencrypt.org/acme/key-change",
"lOPOeUINqls": "Adding random entries to the directory",
"meta": {
"caaIdentities": [
"letsencrypt.org"
],
"termsOfService": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf",
"website": "https://letsencrypt.org"
},
"newAccount": "https://acme-v02.api.letsencrypt.org/acme/new-acct",
"newNonce": "https://acme-v02.api.letsencrypt.org/acme/new-nonce",
"newOrder": "https://acme-v02.api.letsencrypt.org/acme/new-order",
"revokeCert": "https://acme-v02.api.letsencrypt.org/acme/revoke-cert"
- Connection #0 to host acme-v02.api.letsencrypt.org left intact
renew cert result
#certbot renew --dry-run
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/help.cuscapi.com.conf
Cert is due for renewal, auto-renewing...
Plugins selected: Authenticator nginx, Installer nginx
Starting new HTTPS connection (1): acme-staging-v02.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for help.cuscapi.com
Waiting for verification...
Challenge failed for domain help.cuscapi.com
http-01 challenge for help.cuscapi.com
Cleaning up challenges
Attempting to renew cert (help.cuscapi.com) from /etc/letsencrypt/renewal/help.cuscapi.com.conf produced an unexpected error: Some challenges have failed.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/help.cuscapi.com/fullchain.pem (failure)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates below have not been saved.)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/help.cuscapi.com/fullchain.pem (failure)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: help.cuscapi.com
Type: connection
Detail: Fetching
http://help.cuscapi.com/.well-known/acme-challenge/cUig96qUk1MLz3UOKAuDroQI57w3h9dDPMmdhipHEI0:
Timeout during connect (likely firewall problem)To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.