Failed renew certificated expired

Help
1

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: indicadores.camarco.org.ar

I ran this command:
root@camweb:/# certbot renew --dry-run

It produced this output:

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

Processing /etc/letsencrypt/renewal/indicadores.camarco.org.ar.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Running pre-hook command: sudo service nginx stop
Renewing an existing certificate
Performing the following challenges:
Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA.
Attempting to renew cert (indicadores.camarco.org.ar) from /etc/letsencrypt/renewal/indicadores.camarco.org.ar.conf produced an unexpected error: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/indicadores.camarco.org.ar/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/indicadores.camarco.org.ar/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)

Running post-hook command: sudo service nginx start
1 renew failure(s), 0 parse failure(s)

My web server is (include version):

The operating system my web server runs on is (include version): Ubuntu 16.04.6 LTS

I can login to a root shell on my machine

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
certbot 0.31.0

2

Hi @sebabellucci

you have a lot of old certificates. Looks like you have used tls-sni-01 - validation, that's deprecated.

So try

certbot renew --dry-run --nginx

to use your running webserver.

1 Like
3

He's running the standalone plugin, which used to work for him, including pre- and post hooks.

I think it would make things much simpler by just adding --preferred-challenges http to the already used command line.

1 Like
4

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: indicadores.camarco.org.ar
    Type: unauthorized
    Detail: Invalid response from
    http://indicadores.camarco.org.ar/.well-known/acme-challenge/l2M66yFLtB83QWqT BN3f3bdP6ZDKHpK9h0JfXlq4GrE
    [190.104.249.236]: “\n\n403
    Forbidden\n\n

    Forbidden

    \n<p”

    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.

5

Run the same command with -vvv, then you have a long log.

Check that log to see, what redirect Certbot has created. Then check the permissions of that directory.

Or use the webroot ( User Guide — Certbot 2.7.0.dev0 documentation )

But your current configuration ( https://check-your-website.server-daten.de/?q=indicadores.camarco.org.ar )

Domainname Http-Status redirect Sec. G
• http://indicadores.camarco.org.ar/
190.104.249.236 500 0.537 S
Internal Server Error
• https://indicadores.camarco.org.ar/
190.104.249.236 200 2.613 N
Certificate error: RemoteCertificateChainErrors
• http://indicadores.camarco.org.ar/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
190.104.249.236 403 0.514 M
Forbidden
Visible Content: Forbidden You don't have permission to access /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de on this server.

has the same Forbidden. So

  • /.well-known ... is blocked (or)
  • there is already a location definition, so check that and change the permissions
1 Like
6

Hi guys,

Thanks for you helpme!! i fix it using validation for dns. now, workinkg for me

Very Thanks!!

1 Like
7

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