You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was adding my first ingress which was x.domain.com, and the webhook went well.
few minutes later I've added x1.domain.com, and got error in the challenge says:
Accepting challenge authorization failed: acme: authorization error for x1.domain.com: 400 urn:ietf:params:acme:error:dns: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.x1.domain.com - check that a DNS record exists for this domain
The TXT record seem to be created by godaddy webhook, and deleted after 750ms, once it deleted the error (found in the challenge events) the error showed up.
Can we extend the deletion time? anyone familiar with this issue?
If I understand well the issue, this plugin should include an additional parameter in order to add an "extra sleep after adding the TXT record.". I will check the code to see if this doable. You could maybe also propose a PR ;-)
If I understand well the issue, this plugin should include an additional parameter in order to add an "extra sleep after adding the TXT record.". I will check the code to see if this doable. You could maybe also propose a PR ;-)
If you can point me to the relevant place in code, I'll do it. But for now I saw:
I was adding my first ingress which was x.domain.com, and the webhook went well.
few minutes later I've added x1.domain.com, and got error in the challenge says:
The TXT record seem to be created by godaddy webhook, and deleted after 750ms, once it deleted the error (found in the challenge events) the error showed up.
Can we extend the deletion time? anyone familiar with this issue?
Edit: Anyone in here now how to extend the delay? I want to try this by the answer I got: https://community.letsencrypt.org/t/challenge-failed-and-got-error-dns-problem-nxdomain-looking-up-txt/225975/4?u=david-gh
@cmoulliard maybe you can help?
The text was updated successfully, but these errors were encountered: