Renew dry-run don't work / renew is ok

Issuance Tech
1

Hello,
Can you explain to me why the renew -dry-run command didn’t work
while the renew command works fine

perhaps the api acme-staging.api.letsencrypt.org / acme-v01.api.letsencrypt.org ?

with stars like this was command certbot renew --dry-run and certbot renew

certbot renew --dry-run
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/iga.gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for iga.gdts.eu
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (iga.gdts.eu) from /etc/letsencrypt/renewal/iga.gdts.eu .conf produced an unexpected error: Failed authorization procedure. iga.gdts.eu (http-01): urn:acme:error:connection :: The server could not connect to the clie nt to verify the domain :: DNS problem: NXDOMAIN looking up A for iga.gdts.eu. S kipping.

Processing /etc/letsencrypt/renewal/gab.gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for gab.gdts.eu
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (gab.gdts.eu) from /etc/letsencrypt/renewal/gab.gdts.eu .conf produced an unexpected error: Failed authorization procedure. gab.gdts.eu (http-01): urn:acme:error:connection :: The server could not connect to the clie nt to verify the domain :: DNS problem: NXDOMAIN looking up A for gab.gdts.eu. S kipping.

Processing /etc/letsencrypt/renewal/cos.gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for cos.gdts.eu
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (cos.gdts.eu) from /etc/letsencrypt/renewal/cos.gdts.eu .conf produced an unexpected error: Failed authorization procedure. cos.gdts.eu (http-01): urn:acme:error:connection :: The server could not connect to the clie nt to verify the domain :: Fetching http://cos.gdts.eu/.well-known/acme-challeng e/3gvNJTIdv98w8sjmHc9vOk800gFMo1doNU-orbi9fmE: Timeout. Skipping.

Processing /etc/letsencrypt/renewal/zeus.gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for zeus.gdts.eu
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (zeus.gdts.eu) from /etc/letsencrypt/renewal/zeus.gdts. eu.conf produced an unexpected error: Failed authorization procedure. zeus.gdts. eu (http-01): urn:acme:error:connection :: The server could not connect to the c lient to verify the domain :: Fetching http://zeus.gdts.eu/.well-known/acme-chal lenge/JVbTqCTxClHDZFkMVhoEeAeofrsRLFX3Fbzo2bvM1BE: Timeout. Skipping.

Processing /etc/letsencrypt/renewal/gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for gdts.eu
http-01 challenge for www.gdts.eu
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (gdts.eu) from /etc/letsencrypt/renewal/gdts.eu.conf pr oduced an unexpected error: Failed authorization procedure. www.gdts.eu (http-01 ): urn:acme:error:connection :: The server could not connect to the client to ve rify the domain :: Fetching http://www.gdts.eu/.well-known/acme-challenge/89d2FJ I3iBptk9nAVeU_q6CwSgl5v43gBXJ3y8KxfVc: Timeout, gdts.eu (http-01): urn:acme:erro r:connection :: The server could not connect to the client to verify the domain :: Fetching http://gdts.eu/.well-known/acme-challenge/HfOS_L1Z5zRgaSawWH-McyeL58 vBz0Jx1frMDfR45Oo: Timeout. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/iga.gdts.eu/fullchain.pem (failure)
/etc/letsencrypt/live/gab.gdts.eu/fullchain.pem (failure)
/etc/letsencrypt/live/cos.gdts.eu/fullchain.pem (failure)
/etc/letsencrypt/live/zeus.gdts.eu/fullchain.pem (failure)
/etc/letsencrypt/live/gdts.eu/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/iga.gdts.eu/fullchain.pem (failure)
/etc/letsencrypt/live/gab.gdts.eu/fullchain.pem (failure)
/etc/letsencrypt/live/cos.gdts.eu/fullchain.pem (failure)
/etc/letsencrypt/live/zeus.gdts.eu/fullchain.pem (failure)
/etc/letsencrypt/live/gdts.eu/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)

5 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: cos.gdts.eu
    Type: connection
    Detail: Fetching
    http://cos.gdts.eu/.well-known/acme-challenge/3gvNJTIdv98w8sjmHc9vOk800gFMo1d oNU-orbi9fmE:
    Timeout

    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.

  • The following errors were reported by the server:

    Domain: gab.gdts.eu
    Type: connection
    Detail: DNS problem: NXDOMAIN looking up A for gab.gdts.eu

    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.

  • The following errors were reported by the server:

    Domain: iga.gdts.eu
    Type: connection
    Detail: DNS problem: NXDOMAIN looking up A for iga.gdts.eu

    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.

  • The following errors were reported by the server:

    Domain: www.gdts.eu
    Type: connection
    Detail: Fetching
    http://www.gdts.eu/.well-known/acme-challenge/89d2FJI3iBptk9nAVeU_q6CwSgl5v43 gBXJ3y8KxfVc:
    Timeout

    Domain: gdts.eu
    Type: connection
    Detail: Fetching
    http://gdts.eu/.well-known/acme-challenge/HfOS_L1Z5zRgaSawWH-McyeL58vBz0Jx1fr MDfR45Oo:
    Timeout

    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.

  • The following errors were reported by the server:

    Domain: zeus.gdts.eu
    Type: connection
    Detail: Fetching
    http://zeus.gdts.eu/.well-known/acme-challenge/JVbTqCTxClHDZFkMVhoEeAeofrsRLF X3Fbzo2bvM1BE:
    Timeout

    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.

certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/iga.gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for iga.gdts.eu
Waiting for verification…
Cleaning up challenges

new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/iga.gdts.eu/fullchain.pem

Processing /etc/letsencrypt/renewal/gab.gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for gab.gdts.eu
Waiting for verification…
Cleaning up challenges

new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/gab.gdts.eu/fullchain.pem

Processing /etc/letsencrypt/renewal/cos.gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for cos.gdts.eu
Waiting for verification…
Cleaning up challenges

new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/cos.gdts.eu/fullchain.pem

Processing /etc/letsencrypt/renewal/zeus.gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for zeus.gdts.eu
Waiting for verification…
Cleaning up challenges

new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/zeus.gdts.eu/fullchain.pem

Processing /etc/letsencrypt/renewal/gdts.eu.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for gdts.eu
http-01 challenge for www.gdts.eu
Waiting for verification…
Cleaning up challenges

new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/gdts.eu/fullchain.pem

Congratulations, all renewals succeeded. The following certs have been renewed:
/etc/letsencrypt/live/iga.gdts.eu/fullchain.pem (success)
/etc/letsencrypt/live/gab.gdts.eu/fullchain.pem (success)
/etc/letsencrypt/live/cos.gdts.eu/fullchain.pem (success)
/etc/letsencrypt/live/zeus.gdts.eu/fullchain.pem (success)
/etc/letsencrypt/live/gdts.eu/fullchain.pem (success)

Best regards
Julien

2

Hi @jume,

For a couple of these (those with the NXDOMAIN error), the host name literally does not exist in the DNS. So the DNS records should be updated to restore the record for those hosts.

The Timeout errors are a more puzzling problem. This could be caused by a wide range of things, but the most obvious sources of error probably don’t apply to your situation. For example, these hosts advertise AAAA records for IPv6 connectivity, while many hosts that advertise such records refuse inbound IPv6 connections. But your hosts seem to work properly in IPv6.

Are the spaces in the URLs (like “chal lenge”) actually present in your Certbot output, or were they added somehow by the method you used to paste the output into the forum?

Do you know of any host or network firewall rules that would forbid inbound connections on port 80 in either IPv4 or IPv6 from certain IP address ranges?

Have you changed anything related to this since you tried the renewal? (If you went to one of the challenge file addresses in a browser right at the time you were trying the renewal, would it work properly at that moment?)

1 Like
3

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