Open Minecodes opened 6 days ago
This is very little information to understand the issue, but it looks like the TXT record is not properly updated. This is quite likely a configuration error. Could you share your configuration and more logs?
2024/07/05 13:21:44.685 INFO tls.obtain acquiring lock {"identifier": "minecodes.de"}
2024/07/05 13:21:44.687 INFO tls storage cleaning happened too recently; skipping for now {"storage": "FileStorage:/home/thies/Website/certs/", "instance": "5232d68e-9859-4ffe-a507-587fac784fbf", "try_again": "2024/07/06 13:21:44.687", "try_again_in": 86399.999999038}
2024/07/05 13:21:44.687 INFO tls.obtain lock acquired {"identifier": "minecodes.de"}
2024/07/05 13:21:44.687 INFO tls finished cleaning storage units
2024/07/05 13:21:44.687 INFO tls.obtain obtaining certificate {"identifier": "minecodes.de"}
2024/07/05 13:21:44.688 INFO tls.issuance.acme waiting on internal rate limiter {"identifiers": ["minecodes.de"], "ca": "https://acme-staging-v02.api.letsencrypt.org/directory", "account": "contact@minecodes.de"}
2024/07/05 13:21:44.688 INFO tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["minecodes.de"], "ca": "https://acme-staging-v02.api.letsencrypt.org/directory", "account": "contact@minecodes.de"}
2024/07/05 13:21:44.688 INFO tls.issuance.acme using ACME account {"account_id": "https://acme-staging-v02.api.letsencrypt.org/acme/acct/154007433", "account_contact": ["mailto:contact@minecodes.de"]}
2024/07/05 13:21:45.750 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "minecodes.de", "challenge_type": "dns-01", "ca": "https://acme-staging-v02.api.letsencrypt.org/directory"}
2024/07/05 13:22:53.166 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "minecodes.de", "challenge_type": "dns-01", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "No TXT record found at _acme-challenge.minecodes.de", "instance": "", "subproblems": []}}
2024/07/05 13:22:53.166 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "minecodes.de", "problem": {"type": "urn:ietf:params:acme:error:unauthorized", "title": "", "detail": "No TXT record found at _acme-challenge.minecodes.de", "instance": "", "subproblems": []}, "order": "https://acme-staging-v02.api.letsencrypt.org/acme/order/154007433/17609697553", "attempt": 1, "max_attempts": 3}
2024/07/05 13:22:53.166 ERROR tls.obtain could not get certificate from issuer {"identifier": "minecodes.de", "issuer": "acme-staging-v02.api.letsencrypt.org-directory", "error": "HTTP 403 urn:ietf:params:acme:error:unauthorized - No TXT record found at _acme-challenge.minecodes.de"}
I cleaned all records to make a fresh attempt to make it as reproducible as possible. It still has the same outcome
Can you also share your configuration? From a first look, the DNS record is not updated. That is, the desec provider is not used at all.
example.com {
tls contact@example.com {
dns desec {
token "Token"
}
}
respond * "In maintainance" 200
}
This is what I used in the config
I don't know if this affects everyone, but every time I use this plugin for the DNS challenge, I get this error:
With Cloudflare, it's working fine (other domain). I'm currently trying to pin down the problem using the staging server. Could anyone tell me what happened there?