Acme Certificate: Add txt record error

Everything was working when I set this up but I must have changed somewhere.

Guacamole
Renewing certificate
account: WEBGUI_KEYS
server: letsencrypt-production-2

/usr/local/pkg/acme/acme.sh --issue --domain ‘connections.mysite.com’ --dns ‘dns_cf’ --home ‘/tmp/acme/Guacamole/’ --accountconf ‘/tmp/acme/Guacamole/accountconf.conf’ --force --reloadCmd ‘/tmp/acme/Guacamole/reloadcmd.sh’ --log-level 3 --log ‘/tmp/acme/Guacamole/acme_issuecert.log’
Array
(
[path] => /etc:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin/
[PATH] => /etc:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin/
[CF_Key] => ---------------------
[CF_Email] => my@email.com
[CF_Token] => ---------------------
[CF_Account_ID] => ---------------------
[CF_Zone_ID] => ---------------------------------
)
[Sun Jul 2 21:22:06 NZST 2023] Using CA: https://acme-v02.api.letsencrypt.org/directory
[Sun Jul 2 21:22:07 NZST 2023] Registering account: https://acme-v02.api.letsencrypt.org/directory
[Sun Jul 2 21:22:09 NZST 2023] Already registered
[Sun Jul 2 21:22:09 NZST 2023] ACCOUNT_THUMBPRINT=‘----------------------------’
[Sun Jul 2 21:22:09 NZST 2023] Single domain=‘connections.mysite.com
[Sun Jul 2 21:22:09 NZST 2023] Getting domain auth token for each domain
[Sun Jul 2 21:22:10 NZST 2023] Getting webroot for domain=‘connections.mysite.com
[Sun Jul 2 21:22:10 NZST 2023] Adding txt value: --------- for domain: _acme-challenge.connections.mysite.com
[Sun Jul 2 21:22:11 NZST 2023] Adding record
[Sun Jul 2 21:22:12 NZST 2023] Add txt record error.
[Sun Jul 2 21:22:12 NZST 2023] Error add txt for domain:_acme-challenge.connections.mysite.com
[Sun Jul 2 21:22:12 NZST 2023] Please check log file for more details: /tmp/acme/Guacamole/acme_issuecert.log

The method I am using is DNS-Cloudflare

The error log is a bit beyond me my has the following error entries at various points:

  • ‘dns_cf’ does not contain ‘dns’
  • ‘dns_cf’ does not contain ‘no’
  • ‘dns_cf’ does not contain ‘apache’
  • config file is empty, can not read CA_KEY_HASH

But then heaps of processing seems to take place and the file ends much later with:

[Sun Jul 2 21:22:13 NZST 2023] code=‘200’
[Sun Jul 2 21:22:13 NZST 2023] original=‘{
“type”: “dns-01”,
“status”: “pending”,
“url”: “https://acme-v02.api.letsencrypt.org/acme/chall-v3/-/---”,
“token”: ------------------
}’
[Sun Jul 2 21:22:13 NZST 2023] _json_decode
[Sun Jul 2 21:22:13 NZST 2023] _j_str=‘{
“type”: “dns-01”,
“status”: “pending”,
“url”: “https://acme-v02.api.letsencrypt.org/acme/chall-v3/-/---”,
“token”: ----------
}’
[Sun Jul 2 21:22:13 NZST 2023] response=‘{“type”:“dns-01”,“status”:“pending”,“url”:“https://acme-v02.api.letsencrypt.org/acme/chall-v3/-/---“,“token”:”----------”}’
[Sun Jul 2 21:22:13 NZST 2023] pid
[Sun Jul 2 21:22:13 NZST 2023] No need to restore nginx, skip.
[Sun Jul 2 21:22:13 NZST 2023] _clearupdns
[Sun Jul 2 21:22:13 NZST 2023] dns_entries
[Sun Jul 2 21:22:13 NZST 2023] skip dns.