<p>I followed the <a href="https://cert-manager.io/docs/tutorials/acme/ingress/" rel="nofollow noreferrer">cert-manager tutorial</a> to enable tls in my <strong>k3s cluster</strong>. So I modified the letsencrypt-staging issuer file to look like this:</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
    name: letsencrypt-staging
spec:
    acme:
        # The ACME server URL
        server: https://acme-staging-v02.api.letsencrypt.org/directory
        # Email address used for ACME registration
        email: mail@example.com
        # Name of a secret used to store the ACME account private key
        privateKeySecretRef:
            name: letsencrypt-staging
        # Enable the HTTP-01 challenge provider
        solvers:
        - http01:
            ingress:
                class: traefik
</code></pre>
<p>but when I deploy it, I get the error <code> Failed to verify ACME account: Get &quot;https://acme-staging-v02.api.letsencrypt.org/directory&quot;: read tcp 10.42.0.96:45732-&gt;172.65.46.172:443: read: connection reset by peer</code>. But thats only with the staging clusterIssuer. The production example from te tutorial works flawlessly. I resacherd this error and it seems to be somthing with the kubernetes dns but I don't know how to test the dns or any other way to figure this error out.</p>
<hr />
<p>Tested the kubernetes DNS and it is up and running, so it must be an error with cert-manager,especially because the <code>prod</code> certificates status says `Ready=True</p>

8bit
<p>So it seems like I ran into a let's encrypt limit. After waiting for a day, the certificate now works</p>
