Closed Woitekku closed 6 months ago
Are there any updates regarding this bug?
Thank you!
It works for me using this exact setup (digicert + HTTP01)
@tibers how did you install cert-manager? via operators hub?
The helm chart.
Seems like your certificate trust store does not contain the public certs for digicert.com. Did you specify a caBundle value?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to jetstack.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to jetstack.
/close
@jetstack-bot: Closing this issue.
Describe the bug:
Unable to setup Issuer/ClusterIssuer when Cert-Manager is installed via HELM. On the very same cluster/setup it works like a charm if Cert-Manager is installed via Operator Hub.
The error it returns:
Expected behaviour:
Register ACME account with ACME server and get Issuer ready to get certificates.
Steps to reproduce the bug:
Anything else we need to know?:
Environment details::
/kind bug