Custom wildcard certificate - not working as expected

Traefik Traefik v2
1

Hi, I'm using Traefik v2 on a docker container.
I succesfully configured Home Assistant using online documentation, with a custom wildcard certificate and it's working great.
Now I'm replicating the previous configuration to publish more services, but the browser gets "TRAEFIK DEFAULT CERTIFICATE" instead of mine.
Please advise how to fix the config.
traefik.yml

## traefik.yml

### STATIC CONFIG ###
log:
  level: WARNING

api:
  insecure: true
  dashboard: true

providers:
  docker:
    endpoint: "unix:///var/run/docker.sock"
    exposedByDefault: false
  file:
    filename: "/etc/traefik/traefik.yml"

# EntryPoints
## Hassos
entryPoints:
  cloudflare-2083:
    address: ":2083"
  web-secure:
     address: ":443"

### DYNAMIC CONFIG ###

# Routers
## Hassos
http:
  routers:
    router-hassos:
      entryPoints:
        - "cloudflare-2083"
      service: service-hassos
      rule: "Host(`ha.myself.it`)"
      tls: {}
    router-adminer:
      entryPoints:
        - "web-secure"
      service: service-adminer
      rule: "Host(`adminer.lab.myself.it`)"
      tls: {}

# Services
## Hassos
  services:
    service-hassos:
      loadBalancer:
        servers:
          - url: "http://hassos.lab.myself.it:8123"
## Adminer
    service-adminer:
      loadBalancer:
        servers:
          - url: "http://pdocker01.lab.myself.it:8383"

tls:
  certificates:
    - certFile: /etc/ssl/star_myself_it/domain.crt
      keyFile: /etc/ssl/star_myself_it/domain.key
      stores:
        - default

Please note that myself.it is my public domain, while lab.myself.it is my internal domain which I use only from the LAN. I know that I have to add a rule to adminer to prevent access from outside, but that will come later.

1 Like
2

The same problem appears at my config. I would appreciate any working solution for this too.

3

My problem is that wildcard certificates cannot be used for 4th level domain like admirer.lab.myself.it

4

I'm having the same problem right now. Did you solve it @mlazzarotto ?

5

I was trying to use a wildcard certificate on a 4th level domain. This is simply not possible because wildcard certificates can be used up to 3rd level.
adminer.lab.myself.it NO
lab.myself.it YES