Wildcard SSL Cert not working on Ingress

Rancher 2.x
1

Rancher 2.2.1

Hi I have installed a Certificated which is a wildcard certificate.
*.sbox.mydomain.com

I added this in the loadbanacer section of Rancher to the App Ingress.
added doamin test.sbox.mydoamin.com and when loading the url i’m getting a certificate error: Kubernetes Ingress Controller Fake Certificate.

Any idea what I’m doing wrong ?
There service is available on test.sbox.mydoamin.com via HTTP plain.

2

I have the same problem with rancher 2.1.8

3

Hello Michal,

did you manage to fix the problem? I’m experiencing the same issue with my brand new wildcard certificate on rancher 2.1.7.
Do you have any clue on how to fix this?

Thanks!

4

By any chance, did you miss the radio button for “Choose a certificate”? The Certificate dropdown will show you the first certificate it sees, leading you to believe that it will use that one, but it does not use it unless you select the other radio button.

17%20AM
17%20AM1224×362 25.6 KB

If you have correctly selected that, then you can try viewing the YAML of the Ingress and make sure that it has the correct settings.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  ...
spec:
  rules:
  - host: servername.mydomain.com                       <<<
    http:
      paths:
      - backend:
          serviceName: ingress-lsakdj092
          servicePort: 8090
  tls:                                                  <<<
  - hosts:                                              <<<
    - servername.mydomain.com                           <<<
    secretName: cert-wildcard                           <<<
status:
  loadBalancer:
    ingress:
    - ip: ip1
    - ip: ip2

Lastly, I presume that you are browsing to the actual hostname test.sbox.mydoamin.com and not by IP address. Ingresses will only work correctly by going to the hostname.

5

hello shubbard343,
thanks a lot for your feedback. I got the point… indeed I left the default radio choice on…

thanks again!!
Marco