Dns-challenges: certbot.errors.FailedChallenges: Failed authorization procedure

Help
1

I use the same command since years suddenly the renewal does not work.
Please help!

My domain is: signage-network.app

I ran this command:
sudo certbot certonly --manual --debug -d signage-network.app -d *.signage-network.app --agree-tos --manual-public-ip-logging-ok --preferred-challenges dns-01

It produced this output:

Please deploy a DNS TXT record under the name
_acme-challenge.signage-network.app with the following value:

inG9eQdAXmYaxyuPTR2ud417Dalwpz8nZm0E8NXnAAs

Before continuing, verify the record is deployed.

Press Enter to Continue

Please deploy a DNS TXT record under the name
_acme-challenge.signage-network.app with the following value:

JgBDzRmMHRGThrTvsjxSUtTCTNkxD-Xi652n37WYqYM

Before continuing, verify the record is deployed.
(This must be set up in addition to the previous challenges; do not remove,
replace, or undo the previous challenge tasks yet. Note that you might be
asked to create multiple distinct TXT records with the same name. This is
permitted by DNS standards.)

Press Enter to Continue
Waiting for verification...
Cleaning up challenges
Exiting abnormally:
Traceback (most recent call last):
File "/usr/bin/certbot", line 11, in
load_entry_point('certbot==0.31.0', 'console_scripts', 'certbot')()
File "/usr/lib/python3/dist-packages/certbot/main.py", line 1365, in main
return config.func(config, plugins)
File "/usr/lib/python3/dist-packages/certbot/main.py", line 1250, in certonly
lineage = _get_and_save_cert(le_client, config, domains, certname, lineage)
File "/usr/lib/python3/dist-packages/certbot/main.py", line 116, in _get_and_save_cert
renewal.renew_cert(config, domains, le_client, lineage)
File "/usr/lib/python3/dist-packages/certbot/renewal.py", line 323, in renew_cert
new_cert, new_chain, new_key, _ = le_client.obtain_certificate(domains, new_key)
File "/usr/lib/python3/dist-packages/certbot/client.py", line 353, in obtain_certificate
orderr = self._get_order_and_authorizations(csr.data, self.config.allow_subset_of_names)
File "/usr/lib/python3/dist-packages/certbot/client.py", line 389, in _get_order_and_authorizations
authzr = self.auth_handler.handle_authorizations(orderr, best_effort)
File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 82, in handle_authorizations
self._respond(aauthzrs, resp, best_effort)
File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 168, in _respond
self._poll_challenges(aauthzrs, chall_update, best_effort)
File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 239, in _poll_challenges
raise errors.FailedChallenges(all_failed_achalls)
certbot.errors.FailedChallenges: Failed authorization procedure. signage-network.app (dns-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: No TXT record found at _acme-challenge.signage-network.app, signage-network.app (dns-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: No TXT record found at _acme-challenge.signage-network.app
Please see the logfiles in /var/log/letsencrypt for more details.

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: signage-network.app
    Type: unauthorized
    Detail: No TXT record found at _acme-challenge.signage-network.app

    Domain: signage-network.app
    Type: unauthorized
    Detail: No TXT record found at _acme-challenge.signage-network.app

    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.

My web server is (include version): nginx

The operating system my web server runs on is (include version): ubuntu 16.04

My hosting provider, if applicable, is: aws

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

2

That operating system is over two and a half years past its end of life. Even it's direct replacement is over six months past its end of life. You need to implement a much more aggressive operating system upgrade schedule.

This is also an ancient version that is over five years old!

I would first invest my time getting the OS up to a currently supported version before spending the time investigating why the TXT records for the DNS-01 challenge are not being created.

As your certificate has an expiration pending in four days, you may want to manually issue a new certificate to buy yourself a little time to perform your long overdue system maintenance.

You may need to use another ACME client if you aren't able to identify your certbot issue.

3 Likes
3

I agree with linkp about your very old software.

As for the TXT problem a fix may be easy. You have a very large number of TXT records in your DNS (more than 75). An excess will cause Let's Encrypt to fail the validation from a too-large package. Here is just a partial list of your TXT records

Delete all those old records and retry your manual cert request

 dig TXT _acme-challenge.signage-network.app
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> TXT _acme-challenge.signage-network.app
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16297
;; flags: qr rd ra; QUERY: 1, ANSWER: 77, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;_acme-challenge.signage-network.app. IN        TXT

;; ANSWER SECTION:
_acme-challenge.signage-network.app. 96 IN TXT  "5DV436bdxWx-0qCJz-rIsMxODvxUw9wL7x9N2su1iZw"
_acme-challenge.signage-network.app. 96 IN TXT  "P3e35dZ5MMnf_E_CET7AdcJ_6v53lNoEMkhMo_ZLXmw"
_acme-challenge.signage-network.app. 96 IN TXT  "GJ_d6-ttAMf7z2uveY5qmMbBjIiPj47YLg86VYnnCiA"
_acme-challenge.signage-network.app. 96 IN TXT  "PLboZ0Kq9XUPhZFYn3yDVlkBibpBUkRpq-nqYUsWNbk"
_acme-challenge.signage-network.app. 96 IN TXT  "3BG1vanQyBf6utkz1XG-lFAioDEn_qmfhPlHWWZASdw"
5 Likes
4

Well... at least we know the TXT record insertion process works!
Now we just need to work on the deletion/cleanup process - LOL

2 Likes
5

Yeah - manually :slight_smile:

3 Likes
6

Thank you I removed all the old entries than it worked!

4 Likes
7

Thank you for the hint, I updated the server and Certbot version but this was not the solution to the issue. But it was certainly still important that I finally did that :wink:

4 Likes
8

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