title: Cert-manager "remote error: tls: unrecognized name" errors
body: <p>I'm having an issue trying to create certs with cert-manager in a GKE cluster. This has to be something I am doing on my end as I have tried versions, 1.7.1, 1.7.0, and 1.6.2 with all getting the same error.</p>
  <p>The error I am seeing is:</p>
  <pre><code>E0219 00:57:39.270717       1 sync.go:186] cert-manager/controller/challenges &quot;msg&quot;=&quot;propagation check failed&quot; &quot;error&quot;=&quot;failed to perform self check GET request 'http://mysubdomain.mmydomain.com/.well-known/acme-challenge/secretKey': Get \&quot;https://mysubdomain.mmydomain.com:443/.well-known/acme-challenge/secretKey\&quot;: remote error: tls: unrecognized name&quot; &quot;dnsName&quot;=&quot;mysubdomain.mmydomain.com&quot; &quot;resource_kind&quot;=&quot;Challenge&quot; &quot;resource_name&quot;=&quot;elasticsearch-tls-cert-somenumbers&quot; &quot;resource_namespace&quot;=&quot;elastic-stack&quot; &quot;resource_version&quot;=&quot;v1&quot; &quot;type&quot;=&quot;HTTP-01&quot;
  </code></pre>
  <p>This is the setup I went though to install:</p>
  <p>Install CRDs
  <code>kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml</code></p>
  <p>Helm install cert-manager</p>
  <pre><code>helm install \
    cert-manager jetstack/cert-manager \
    --namespace cert-manager \
    --create-namespace \
    --version v1.7.1
  </code></pre>
  <p>Confirmed install is good:</p>
  <pre><code>➜  ~ helm list -n cert-manager
  NAME            NAMESPACE       REVISION    UPDATED                                 STATUS      CHART               APP VERSION
  cert-manager    cert-manager    1           2022-02-18 16:07:57.258172 -0800 PST    deployed    cert-manager-v1.6.2 v1.6.2
  ➜  ~
  </code></pre>
  <p>Applied the ClusterIssuer:</p>
  <pre><code>apiVersion: cert-manager.io/v1
  kind: ClusterIssuer
  metadata:
    name: letsencrypt
  spec:
    acme:
      email: &quot;myemail@myemail.com&quot;
      server: https://acme-v02.api.letsencrypt.org/directory
      privateKeySecretRef:
        name: letsencrypt
      solvers:
      - http01:
          ingress:
            class: nginx
  </code></pre>
  <p>Deployed my ingress:</p>
  <pre><code>apiVersion: networking.k8s.io/v1beta1
  kind: Ingress
  metadata:
    name: kibana-ingress
    namespace: elastic-stack
    annotations:
      cert-manager.io/cluster-issuer: letsencrypt
      kubernetes.io/ingress.class: nginx
      nginx.ingress.kubernetes.io/backend-protocol: &quot;HTTP&quot;
  spec:
    rules:
    - host: mysubdomain.mmydomain.com
      http:
        paths:
        - path: /
          backend:
            serviceName: kibana-kb-http
            servicePort: 5601
    tls:
      - hosts:
        - mysubdomain.mmydomain.com
        secretName: kibana-tls-cert
  </code></pre>
  <p>Then when I tail the cert-manager pods I see the <code>remote error: tls: unrecognized name&quot; &quot;dnsName</code> error.</p>
  <p>A describe of the cert challenge says the same thing:</p>
  <pre><code>Status:
    Presented:   true
    Processing:  true
    Reason:      Waiting for HTTP-01 challenge propagation: failed to perform self check GET request 'http://mysubdomain.mmydomain.com/.well-known/acme-challenge/secretKey': Get &quot;https://mysubdomain.mmydomain.com:443/.well-known/acme-challenge/secretKey&quot;: remote error: tls: unrecognized name
    State:       pending
  Events:
    Type    Reason     Age    From          Message
    ----    ------     ----   ----          -------
    Normal  Started    8m45s  cert-manager  Challenge scheduled for processing
    Normal  Presented  8m45s  cert-manager  Presented challenge using HTTP-01 challenge mechanism
  </code></pre>
  <p>This works totally fine in another cluster, so I cannot figure out what I am doing wrong here.</p>