# \[noob\] - traefic sticking to default certificate

**URL:** <https://community.traefik.io/t/noob-traefic-sticking-to-default-certificate/27046>\
**Category:** Traefik v3 (latest)\
**Tags:** docker\
**Created:** [March 29, 2025, 8:26am UTC](https://community.traefik.io/t/noob-traefic-sticking-to-default-certificate/27046 "2025-03-29T08:26:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Startide](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@Startide](https://community.traefik.io/u/Startide)\
**Post date:** [March 29, 2025, 8:26am UTC](https://community.traefik.io/t/noob-traefic-sticking-to-default-certificate/27046/1 "2025-03-29T08:26:24Z")

</div>

Greetings all !

So I am new to this, and found this tutorial : [https://youtu.be/n1vOfdz5Nm8](https://youtu.be/n1vOfdz5Nm8) to guide me through the process of having proper https certificates for my homelab / nas.

I followed through the steps, but when checking for traefik certificate it says it's using it's own certificate, and not the proper one.

When checking the docker container logs, this is what I find :

```auto

2025-03-29T07:58:16.282879090Z 2025-03-29T08:58:16+01:00 ERR Unable to obtain ACME certificate for domains error="unable to generate a certificate for the domains [local.test.fr *.local.test.fr]: error: one or more domains had a problem:\n[*.local.test.fr] invalid authorization: acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.local.test.fr - check that a DNS record exists for this domain\n[local.test.fr] invalid authorization: acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.local.test.fr - check that a DNS record exists for this domain\n" ACME CA=https://acme-staging-v02.api.letsencrypt.org/directory acmeCA=https://acme-staging-v02.api.letsencrypt.org/directory domains=["local.test.fr","*.local.test.fr"] providerName=cloudflare.acme routerName=traefik-secure@docker rule=Host(`traefik-dashboard.local.test.fr`)
2025-03-29T08:04:44.496672517Z 2025-03-29T09:04:44+01:00 ERR error="accept tcp [::]:443: use of closed network connection" entryPointName=https
2025-03-29T08:04:44.496715817Z 2025-03-29T09:04:44+01:00 ERR error="accept tcp [::]:80: use of closed network connection" entryPointName=http
2025-03-29T08:04:44.496740547Z 2025-03-29T09:04:44+01:00 ERR error="close tcp [::]:80: use of closed network connection" entryPointName=http
2025-03-29T08:04:44.497900631Z 2025-03-29T09:04:44+01:00 ERR error="close tcp [::]:443: use of closed network connection" entryPointName=https

```

Can you guys help me figure out what I am doing wrong ? I have opened the port toward my local server IP for 80 & 443, but no dice so far.

Thanks !

---

<div class="post-metadata">

**Author:** ![bluepuma77](https://avatars.discourse-cdn.com/v4/letter/b/a9adbd/32.png) [@bluepuma77](https://community.traefik.io/u/bluepuma77)\
**Post date:** [March 31, 2025, 12:02pm UTC](https://community.traefik.io/t/noob-traefic-sticking-to-default-certificate/27046/2 "2025-03-31T12:02:07Z")

</div>

Hello, we try to support, but don't watch videos. So you need to share your current Traefik static and dynamic config, and Docker compose file(s) if used.

From a first look, the LetsEncrypt DNS validation is failing, did you create a `local.test.fr` sub-domain with your DNS provider?

Maybe compare to [simple Traefik dnsChallenge example](https://github.com/bluepuma77/traefik-best-practice/tree/main/docker-traefik-dnschallenge) and other folders in the repo.

---

<div class="post-metadata">

**Author:** ![Startide](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@Startide](https://community.traefik.io/u/Startide)\
**Post date:** [March 31, 2025, 12:42pm UTC](https://community.traefik.io/t/noob-traefic-sticking-to-default-certificate/27046/3 "2025-03-31T12:42:26Z")

</div>

Thanks a bunch, not sure why but it ended up working somehow. I can now access my local url. I think it was a problem with dns not properly propagating across my registrar / cloudflare.