Traefik not generating SSL Certs

Wappler General Bugs
1

Wappler Version : 6.5.2
Operating System : Windows 11 Pro
Server Model: NodeJS
Database Type: MariaDB
Hosting Type: Docker Custom

Expected behavior

What do you think should happen?

When deploying Traefik, SSL Certs for itself and other projects should generate a SSL certificate

Actual behavior

What actually happens?

No SSL Cert is generated, acme.json file shows “null” in the certificates section

How to reproduce

  • Detail a step by step guide to reproduce the issue
  • A screenshot or short video indicating the problem
  • A copy of your code would help. Include: JS, HTML.
  • Test your steps on a clean page to see if you still have an issue

Due to ongoing issues with this issue here - Project Missing Multiple Docker Targets I am trying now to migrate to a new docker target since I cannot fix that issue or deploy new projects. I have the new server up and running, system checks verified. Deployed project to that target successfully, deployed Traefik successfully. However, Traefik will not generate any certificates, either for itself or the other project. I can see inside the Traefik dashboard it is showing the URLs correctly for itself and the other project. Checking the /var/lib/docker/volumes/wappler-compose_letsencrypt/_data/acme.json file it does not update nor show the websites there and shows as null. I modified the email fields and key fields, the rest is what is in there now.

  "leresolver": {
    "Account": {
      "Email": "EMAILREMOVED",
      "Registration": {
        "body": {
          "status": "valid",
          "contact": [
            "mailto:EMAILREMOVED"
          ]
        },
        "uri": "https://acme-v02.api.letsencrypt.org/acme/acct/1701963837"
      },
      "PrivateKey": "KEYREMOVED",
      "KeyType": "4096"
    },
    "Certificates": null
  }
}

I have tried removing and re-adding traefik, redeploying, so far no changes.

Ports 80, 443 are open.

Any assistance is appreciated. Thanks

2

By any chance is the domain proxied by Cloudflare? If so then you will need to pause Cloudflare for the domain so certbot can issue the certificates…

3

Not proxied by CloudFlare, using AWS Route53 but this domain is not behind a CloudFront distribution either.

4

If I remember from my AWS experience Route 53 was a pain in the arse with LetsEncrypt (required user permissions and installation of the Certbot plugin). I’m pretty sure we used Amazon’s own Certificate Manager console to do it as for some reason had bookmarked the following video:

5

Have not had any issues with my other docker target, also hosted in the same location. Basically a duplicate aside from a different static IP which is why I am confused why one is working and one is not.

Also, not hosting with EC2

6

Then I’d suggest deploying and leaving it for a couple of hours to see if the certificates are propagated? May just take a little time.

7

Will try waiting, its a bit annoying since I could deploy on the other docker target and it would have a certificate within 1-2 minutes on a new domain I just created.

8

Will always be that one Project that we need to get done but it just refuses to play the game! We know that feeling very well. Usually all comes good in the end with a little waiting, a cup or two of coffee…

:slight_smile:

9

I just wish I could fix the problem in my other thread, seems the docker setup is completely broken across all my projects with volumes becoming unlinked thus me setting up a new docker target but with other issues now on the new target.

10

Well apparently I was too impatient as you said. Waited a few hours already before posting this thread but I guess I need another hour to wait and now they have their certs.

Ah well, will leave this up anyways to remind other people to be patient as well.

1 Like