-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
first try to generate cert always fail #4
Comments
I had the same behaviour, any update ? |
I'm getting something very similar.
|
Tried with a new token and I got the same error as @sherlant
|
I think the issue might be related to the "API Key" vs PAT. "API Key":
PAT:
|
If I use Postman or |
Thanks @bittermandel for your answer. I created a PAT with the same permissions. My
I'm running out of idea. |
Can you try removing the cnameStrategy field completely and see if it helps? |
It changed nothing but I deleted all the
EDIT: I was using the original repository for years successfully. |
According to the
|
If I create the |
Can you send the full log of the webhook please? or if you can make it reproducible. We changed minor details when we forked to allow CName follows, so it's likely that causing issues. |
To clarify the rootDomain functionality: If you want to always use the same domain, do not set rootDomain and you would get a record for only the ingress' domain. |
Steps to reproduce with
|
Thanks! |
I tried without
Here are the Kubernetes evens related to the challenge.
|
That is very helpful, thank you! I will have to make a patch to fix that. You can revert to an older version if you’d like to progress before I’m able to fix it. |
Thanks @bittermandel 👍 |
Hi,
when i use cert-manager-webhook-gandi to create a cert, the first try always fail. And when i use the cert-manger cli to force renew the certificate, this is ok.
I see that the first challenge is ok, but the second fail first time with message :
'Error accepting authorization: acme: authorization error for test2.my-domain.io: 403 urn:ietf:params:acme:error:unauthorized: During secondary validation: Incorrect TXT record "XXXXXXXXXX" found at _acme-challenge.test2.my-domain.io''
I don't understead. I don't have another 403 error when i submit the same cert with the cli, just after the first try.
I don't see anything in logs.
Can you please help me ?
The text was updated successfully, but these errors were encountered: