Order and challenge pending with wrong status code 426, expected 200 #6198
Unanswered
andrasnemethcg
asked this question in
Q&A
Replies: 2 comments 1 reply
-
The cm-acme-http-resolver ingress does not get the ingressClassName in Spec. When manually edited the ingress resource, it started to work. It is a hack that got us new certificate, but only a temporary solution. We need to find a way to tell to cert-manager to create the http resolver ingress with a certain ingressClassName. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Fixed on the ingress w annotation |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Our gitlab kas certificate (existed, but failed to renew and now expired) renewal failed with challenge showing "wrong status code 426, expected 200".
We tried to delete the order, which then got automatically recreated (with challenge), but ended up with same error.
There is a cm-acme-http-solver pod with token&key injected via args.
Is the error reported by ACME provider? What may cause the 426 response? How can we find out more?
Thanks in advance!
Here is the challenge:
Beta Was this translation helpful? Give feedback.
All reactions