Domain renewal is not working

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: *.digi-was.com

I ran this command for creating the cert : sudo certbot certonly --manual --preferred-challenges=dns --email roshan.thomas@xxxxxx.com --server https://acme-v02.api.letsencrypt.org/directory --agree-tos -d digi-was.com -d *.digi-was.com
For renewal : sudo certbot renew
It produced this output:

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


Processing /etc/letsencrypt/renewal/digi-was.com.conf


Cert is due for renewal, auto-renewing...

Plugins selected: Authenticator certbot-plugin-gandi:dns, Installer None

Renewing an existing certificate

Performing the following challenges:

dns-01 challenge for digi-was.com

dns-01 challenge for digi-was.com

Unsafe permissions on credentials configuration file: /etc/letsencrypt/gandi.ini

Cleaning up challenges

Unable to find or delete the DNS TXT record: Unable to get base domain for "digi-was.com"

Unable to find or delete the DNS TXT record: Unable to get base domain for "digi-was.com"

Attempting to renew cert (digi-was.com) from /etc/letsencrypt/renewal/digi-was.com.conf produced an unexpected error: An error occurred adding the DNS TXT record: Unable to get base domain for "digi-was.com". Skipping.

All renewal attempts failed. The following certs could not be renewed:

/etc/letsencrypt/live/digi-was.com/fullchain.pem (failure)


All renewal attempts failed. The following certs could not be renewed:

/etc/letsencrypt/live/digi-was.com/fullchain.pem (failure)


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):

My hosting provider, if applicable, is: azure zone

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):

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

digi-was.com is being served by Azure DNS servers, not Gandi. Did you change DNS providers recently?

3 Likes

no , initial provider in Azure only .

Is any thing I missed while cert creation ?

I don't know, you tell me? Your initial cert creation command specified the --manual plugin (which by the way cannot be renewed by running certbot renew without authentication scripts), but for some reason your renewal configuration file at /etc/letsencrypt/renewal/digi-was.com.conf seems to be configured to use the certbot-dns-gandi authenticator plugin? That's just weird.

4 Likes

yes , that I remember some resolution to update the config file for the renewal . I got stuck here . can you give some direction

There also exists a certbot-dns-azure DNS plugin (third party, available on PyPi: certbot-dns-azure · PyPI, docs: Welcome to certbot-dns-azure’s documentation! — certbot-dns-azure 0 documentation). You could perhaps try that as Azure seems to be your DNS provider? Note: I don't know anything about Azure, so YMMV.

2 Likes

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