# Problem installing Rancher with Let´s Encrypt

**URL:** <https://forums.suse.com/t/problem-installing-rancher-with-let-s-encrypt/36729>\
**Category:** SUSE Rancher Prime\
**Created:** [January 14, 2022, 9:54pm UTC](https://forums.suse.com/t/problem-installing-rancher-with-let-s-encrypt/36729 "2022-01-14T21:54:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![svimes](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@svimes](https://forums.suse.com/u/svimes)\
**Post date:** [January 14, 2022, 9:54pm UTC](https://forums.suse.com/t/problem-installing-rancher-with-let-s-encrypt/36729/1 "2022-01-14T21:54:14Z")

</div>

**Provider** : K3S  
**Kubernetes Version** : v1.19.15+k3s2  
**Rancher** : 2.5.9

Hi,

I followed this official guide to install Rancher with Let´s Encrypt:

> **[Install/Upgrade Rancher on a Kubernetes Cluster](https://rancher.com/docs/rancher/v2.5/en/installation/install-rancher-on-k8s/)**
>
> Learn how to install Rancher in development and production environments. Read about single node and high availability installation

but when accessing to the login page the certificate is invalid.  
The issuer is dynamiclistener-ca and not Let´s Encrypt.

_kubectl -n cattle-system describe certificate_

```auto
Name: tls-rancher-ingress
Namespace: cattle-system
Labels: app=rancher
              app.kubernetes.io/managed-by=Helm
              chart=rancher-2.5.9
              heritage=Helm
              release=rancher
Annotations: <none>
API Version: cert-manager.io/v1
Kind: Certificate
Metadata:
  Creation Timestamp: 2021-10-08T19:30:34Z
  Generation: 1
  Managed Fields:
    API Version: cert-manager.io/v1
    Fields Type: FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          .:
          f:app:
          f:app.kubernetes.io/managed-by:
          f:chart:
          f:heritage:
          f:release:
        f:ownerReferences:
          .:
          k:{"uid":"752e1e8a-bdad-4b8a-be5e-b61d22dd0d35"}:
            .:
            f:apiVersion:
            f:blockOwnerDeletion:
            f:controller:
            f:kind:
            f:name:
            f:uid:
      f:spec:
        .:
        f:dnsNames:
        f:issuerRef:
          .:
          f:group:
          f:kind:
          f:name:
        f:privateKey:
        f:secretName:
        f:usages:
      f:status:
        .:
        f:conditions:
        f:notAfter:
        f:notBefore:
        f:renewalTime:
        f:revision:
    Manager: controller
    Operation: Update
    Time: 2021-12-07T19:31:40Z
  Owner References:
    API Version: networking.k8s.io/v1
    Block Owner Deletion: true
    Controller: true
    Kind: Ingress
    Name: rancher
    UID: 752e1e8a-bdad-4b8a-be5e-b61d22dd0d35
  Resource Version: 22473173
  Self Link: /apis/cert-manager.io/v1/namespaces/cattle-system/certificates/tls-rancher-ingress
  UID: 81efa2e6-f970-4731-95f2-3fd1815a9d7b
Spec:
  Dns Names:
    host.example.com
  Issuer Ref:
    Group: cert-manager.io
    Kind: Issuer
    Name: rancher
  Secret Name: tls-rancher-ingress
  Usages:
    digital signature
    key encipherment
Status:
  Conditions:
    Last Transition Time: 2021-10-08T19:31:40Z
    Message: Certificate is up to date and has not expired
    Observed Generation: 1
    Reason: Ready
    Status: True
    Type: Ready
  Not After: 2022-03-07T19:31:40Z
  Not Before: 2021-12-07T19:31:40Z
  Renewal Time: 2022-02-05T19:31:40Z
  Revision: 2
Events: <none>

```

Appreciate any help, thanks!