Richard Wall

Probably not a good idea. The Pebble delays and simulated api errors help test that cert-manager can deal with such erratic behaviour from real ACME servers.

@lunarwhite We have released this. Please test and feedback: https://github.com/cert-manager/cert-manager/releases/tag/v1.19.1

@d-mankowski-synerise @Pionerd We have fixed this. Please test and feedback: https://github.com/cert-manager/cert-manager/releases/tag/v1.19.1

@rubroboletus We have fixed this. Please test and feedback: https://github.com/cert-manager/cert-manager/releases/tag/v1.19.1

@ilsaloving-gander We'll need more information. Share the full examples of Certificate, Issuer, CertificateRequest resources so that we can see the `.status` fields. The status contains information about why the Certificate...

Yes, I think item number 3 is the answer. You need to reconfigure your issuer to use the `sign` endpoint. Update the path field in your Issuer: ``` spec: vault:...

Here's the code: https://github.com/cert-manager/cert-manager/blob/ae14cf6e3caade7256ae85828a41c0329bac377c/internal/vault/vault.go#L142-L183

I agree, this is an easy mistake to make, so cert-manager should give clear error messages and stop if the wrong endpoint is used. I updated the issue title and...

📢 A new pre-release is available which is related to this issue. It fixes the unregulated DigitalOcean retries for errors. * https://github.com/cert-manager/cert-manager/releases/tag/v1.20.0-alpha.0 Please test and report back.

Thanks @DeD1rk. Please create a PR with some proposed additional words for the Helm values documentation. Here's the source: https://github.com/cert-manager/cert-manager/blob/6bb9c743c301c3cbcde1ad052e94ed1fe5ebbd7a/deploy/charts/cert-manager/values.yaml#L975-L1011 You can modify the comments and then run `make generate-helm-docs...