allinkl: cert renewal seems broken #2489
Description
Welcome
- Yes, I'm using a binary release within 2 latest releases.
- Yes, I've searched similar issues on GitHub and didn't find any.
- Yes, I've included all information below (version, config, etc).
What did you expect to see?
I am using all-inkl.com as DNS provider. Renewing certs usually fails for the first time. When retrying for 5 or 10 times at some point it works. Don't know if this is a timeout problem, but at least there seems to be something wrong with the response (unconvertible type in the log, see below).
What did you see instead?
An error message, see below.
How do you use lego?
Binary
Reproduction steps
lego --path path_to_config -a -m [email protected] --dns allinkl --dns-timeout 120 --dns.resolvers ns6.kasserver.com --domains "*.example.com" renew
Effective version of lego
lego version 4.22.2 darwin/arm64Logs
2025/03/19 07:49:59 [INFO] [*.example.com] acme: renewalInfo endpoint indicates that renewal is needed
2025/03/19 07:49:59 [INFO] [*.example.com] acme: Trying renewal with 386 hours remaining
2025/03/19 07:49:59 [INFO] [*.example.com] acme: Obtaining bundled SAN certificate
2025/03/19 07:49:59 [INFO] [*.example.com] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/XXXXXXXXX/XXXXXXXXXX
2025/03/19 07:49:59 [INFO] [*.example.com] acme: use dns-01 solver
2025/03/19 07:49:59 [INFO] [*.example.com] acme: Preparing to solve DNS-01
2025/03/19 07:50:00 [INFO] [*.example.com] acme: Trying to solve DNS-01
2025/03/19 07:50:00 [INFO] [*.example.com] acme: Checking DNS record propagation. [nameservers=ns6.kasserver.com:53]
2025/03/19 07:50:02 [INFO] Wait for propagation [timeout: 1m0s, interval: 2s]
2025/03/19 07:50:02 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:04 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:06 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:08 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:10 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:12 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:14 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:16 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:18 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:20 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:22 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:25 [INFO] [*.example.com] acme: Waiting for DNS record propagation.
2025/03/19 07:50:32 [INFO] [*.example.com] acme: Cleaning DNS-01 challenge
2025/03/19 07:50:33 [WARN] [*.example.com] acme: cleaning up failed: allinkl: response struct decode: decoding failed due to the following error(s):
'Response.ReturnInfo' expected type '%!s(bool=false)', got unconvertible type '""', value: '""'
2025/03/19 07:50:33 [INFO] Deactivating auth: https://acme-v02.api.letsencrypt.org/acme/authz/XXXXXXXXX/XXXXXXXXXX
2025/03/19 07:50:33 error: one or more domains had a problem:
[*.example.com] invalid authorization: acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.example.com - check that a DNS record exists for this domain
Go environment (if applicable)
No response