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
Copy file name to clipboardExpand all lines: content/docs/troubleshooting/acme.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -192,6 +192,8 @@ You can also see some additional information about the state of the [ACME author
192
192
$ kubectl get challenge <challenge-name> -ojsonpath='{.spec.authorizationURL}'
193
193
```
194
194
195
+
In case your Challenge is in the State "errored", once you resolved the underlying issue, you can safely delete it. cert-manager will then request a new Challenge and retry.
196
+
195
197
### HTTP01 troubleshooting
196
198
First of all check if you can see the challenge URL from the public internet, if this does not work check your Ingress and firewall configuration as well as the service and pod cert-manager created to solve the ACME challenge.
197
199
If this does work check if your cluster can see it too. It is important to test this from inside a Pod. If you get a connection error it is suggested to check the cluster's network configuration.
0 commit comments