Traefik using default cert

[sudo-kraken]

All of a sudden traefik isnt working when going to my top level domain i.e. example.com it gives a cert warning issue when you inspect the cert its common name is 'CN=TRAEFIK DEFAULT CERT' whereas all the subdomains which operate on the *.example.com are all fine and work through cloudflare. I have regenereated the acme json and it is still doing this. I dont understand why this is happening as it has been working until today.

[sudo-kraken]

This is the traefik log for when you try to visit the domain, I have changed only the WAN IP and domain name for security reasons

today at 3:26 PM time="2020-04-29T14:26:14Z" level=debug msg="Serving default certificate for request: "example.com""
today at 3:26 PM time="2020-04-29T14:26:15Z" level=debug msg="http: TLS handshake error from x.x.x.x:59639: remote error: tls: bad certificate"

[g0Idfinger]

Does your acme.json show both certificates? example.com and *.example.com

[sudo-kraken]

Does your acme.json show both certificates? example.com and *.example.com

In my traefik 2 acme JSON at the bottom it states certificates: null

[g0Idfinger]

looks like you may need to delete the contents and regenerate it by uncommenting out

• "traefik.http.routers.traefik-rtr.tls.certresolver=dns-cloudflare" and building the traefik container.

[sudo-kraken]

That's what I did I have cycled it twice now the wildcards work but not the top level :(

[sudo-kraken]

Does your traefik 2 acme have certs at the bottom

[g0Idfinger]

mine has this. which is after the private key.

"Certificates": [
  {
    "domain": {
      "main": "domain.com",
      "sans": [
        "*.domain.com"

[sudo-kraken]

I have recreated the SSL as you said to and still nothing ?

[sudo-kraken]

The only thing I can think of that has changed is that I created a new API key for cloudflare ddns but left the global key in the config? Can't see how that would break it though

[sudo-kraken]

Fixed it by removing the image bloody hell this things buggy