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
Hi all. I am running cert manager on kubernetes using a ClusterIssuer. My setup used to work fine until recently.
When I create an ingress , the Challenge remains pending, with an event that reads: Waiting for HTTP-01 challenge propagation: wrong status code '500', expected '200.
I am not sure how to debug this. Can anyone point me in a direction?
The ingress is using nginx-ingress and my endpoint is behind oauth2-proxy, but that did not matter before.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all. I am running cert manager on kubernetes using a ClusterIssuer. My setup used to work fine until recently.
When I create an ingress , the
Challenge
remains pending, with an event that reads:Waiting for HTTP-01 challenge propagation: wrong status code '500', expected '200
.I am not sure how to debug this. Can anyone point me in a direction?
The ingress is using nginx-ingress and my endpoint is behind oauth2-proxy, but that did not matter before.
Beta Was this translation helpful? Give feedback.
All reactions