Error Requesting New Certificate for 1ls.co.uk and *.1ls.co.uk

[jtucker1]

I am writing to report an issue I encountered while requesting a new certificate for my domains 1ls.co.uk and *.1ls.co.uk from Let's Encrypt.

The error message I received is as follows:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Renewing an existing certificate
Performing the following challenges:
dns-01 challenge for 1ls.co.uk
Running manual-auth-hook command: /etc/webmin/webmin/letsencrypt-dns.pl
Waiting for verification...
Challenge failed for domain 1ls.co.uk
dns-01 challenge for 1ls.co.uk
Cleaning up challenges
Running manual-cleanup-hook command: /etc/webmin/webmin/letsencrypt-cleanup.pl
Some challenges have failed.
IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: 1ls.co.uk
   Type:   dns
   Detail: DNS problem: NXDOMAIN looking up TXT for
   _acme-challenge.1ls.co.uk - check that a DNS record exists for this
   domain

I am using virtualmin as my web server control panel, and I noticed that every time certbot successfully retrieves the TXT record information, virtualmin deletes the record and reports an error that there is no such record.

I am unsure how to resolve this issue, and I would appreciate any guidance or assistance you can provide.

Thank you for your time and attention to this matter. I look forward to hearing back from you soon.

Sincerely,
Jon Tucker

[jtucker1]

I have found it is the DNS server not providing the record, in time, for the request.

[Osiris]

See Let's Encrypt DNS challenge method fails when using slave autoconfiguration [#67912] | Virtualmin, the first reply mentions something about a configuration element that adds a delay to the webmin thingy that seems to regulate the dns-01 challenge.

If you don't know how long the DNS provider takes to update the record, try a very long time and make it shorter until it fails and increase it again to a safe timeout.

If that doesn't work, my advice would be to post your issue to the webmin community directly, as not much of our volunteers here have experience with webmin, if any.