Let's Encrypt certificates issues but not loaded when loading url

Renier Duvenhage

Hi

I am using the DNS01 Traefik file with Azure as the provider. The DNS records were added to Azure DNS but then removed after exactly 2 minutes every time. I can also see the requests come through on the activity logs in Azure and then the request to remove the record again.

When I load my site, it is showing that a default certificate is issued but not the domain certificate:

I also did a search and saw that 2 certificates are issued already:

I don't understand what is wrong and why the site is not picking up the correct certificate. I also ran "sudo docker compose logs traefik" and there are no errors or any information in the logs. The site is just not loading any certificates.

I don't know if I've reached the rate limit, but it seems like certificates were issued previously.

I am not sure what else to check to find the potential error?

I've attached the yaml file I am using, just removed the confidential information: docker-compose-dns01-azure-debug.yaml

I am running docker compose version 2.5.1 on Ubuntu 20.04

Allan Zimmermann

Troubleshooting DNS01 issues is just painful.
And you have to be super carefull, you don't get many tries before you hit a rate limit and is locked out for 24 hours or 7 days or 30 days, depending on what you did
Most of the things i would do to troubleshoot this, it seems you already did ( awsome ! ) and they all look good.
Does the information ever end up in the /letsencrypt/acme.json file ?
Check when this was last modified .. this should contain the certificate for this installation to request certificate, and it should contain all the privat ekeys for the different domains lets-encrypt has requested certificates for.
something like this

Allan Zimmermann

Also, traefik is not giving a lot of log information, but it CAN be useful to see the little they do log.
Under traefik -> command: add this at the top

- "--log.level=DEBUG"

Renier Duvenhage

@allan-zimmermann said in Let's Encrypt certificates issues but not loaded when loading url:

"--log.level=DEBUG"

acme.json contains the certificate key values:

When I logged in this morning, the correct certificate were displaying without any changes to the environment after this post. Seems like it just took extremely long to pick it up or my browser cached something (although I closed my browser multiple times during tests).

Allan Zimmermann

@renier-duvenhage Ahh, glad it worked out, even thou we don't know what was wrong. My guess is some rate limited was hit ?
everything else seems correct.