Skip to content

Commit 2f38ef4

Browse files
jplitzaerikgb
authored andcommitted
acme troubleshooting: how to fix errored challenges
Signed-off-by: Jan-Philipp Litza <[email protected]>
1 parent 8d5546a commit 2f38ef4

File tree

1 file changed

+2
-0
lines changed
  • content/docs/troubleshooting

1 file changed

+2
-0
lines changed

content/docs/troubleshooting/acme.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -192,6 +192,8 @@ You can also see some additional information about the state of the [ACME author
192192
$ kubectl get challenge <challenge-name> -ojsonpath='{.spec.authorizationURL}'
193193
```
194194

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+
195197
### HTTP01 troubleshooting
196198
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.
197199
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

Comments
 (0)