Open filipdadgar opened 2 years ago
This is probably due to #6
Thanks, it looks like latest commits have sorted the problem. :)
Looks like another API issue at hands:
Events: Type Reason Age From Message
Normal Started 15m cert-manager-challenges Challenge scheduled for processing Warning PresentError 5m4s (x8 over 15m) cert-manager-challenges Error presenting challenge: unable to create txt-record: Fault(623): Calling parameters do not match signature
Is the old parameter needed again :O ?
Getting the same error, is there a workaround or solution to this?
unable to create txt-record: Fault(623): Calling
parameters do not match signature
I ended up moving my DNS servers to Cloudflare and havent looked back. :)
I might have to do the same thing 😅, too bad that this lib is listed here if it is not updated anymore.
Yeah, but the response times..
Here is a good source: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/cloudflare.md I nowadays tag my services with annotation. Cert and DNS are created on the fly. Signed by letsencrypt. Its almost no fun when it just works. :)
Good luck.
Thanks!
Hi!
Been following the guide but seem to get stuck when the challenge is created:
Solver: dns01: Webhook: Config: Password Secret Key Ref: Key: password Name: loopia-credentials Namespace: adguard Username Secret Key Ref: Key: username Name: loopia-credentials Namespace: adguard Group Name: acme.webhook.loopia.com Solver Name: loopia Token: xxxx Type: DNS-01 URL: https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/xxxx Wildcard: false Status: Presented: false Processing: true Reason: unexpected error: txt-record was not created:
State: pending
Events:
Type Reason Age From Message
Normal Started 13m cert-manager Challenge scheduled for processing Warning PresentError 3m24s (x8 over 13m) cert-manager Error presenting challenge: unexpected error: txt-record was not created:
I have created a "parked" sub dns called adguard.mydomain.com. Do I need to add some data to this record?
Best, Filip