Dokploy / Dokploy/dokploy

Domain certificates are not reliable

Open
#2,399 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

awaiting-feedback
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

To Reproduce

When I assign a new domain to a service I don't know when the certificate for HTTPS is generated. Do I have to deploy or not? Because it doesn't do it instantly because I can look into the acme.json file in the traefik files, right?

Additionally, my traefik logs are somehow getting spammed by errors because some domain couldn't be found or something even tho I removed it long time ago from the service and also it's nowhere in the traefik files.

Image
Current vs. Expected behavior

I expect the certificate to be generated instantly or a hint that I have to redeploy or something. (Or just a bit more information. A "it can take 10min to generate the certificate" is already enough)

And also like a cleanup job. I don't know where the error comes from that there's no A/AAAA records, because this domain is not needed anymore in a service?

Provide environment information
Debian 10.2.1 VPS
Dokploy Version: v0.24.11
Which area(s) are affected? (Select all that apply)

Traefik

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Maybe, need help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue on Dokploy v0.24.11 with Traefik, checking the Traefik logs and acme.json while assigning and removing a domain. Determine the certificate-generation timing, whether redeployment is required, and why removed domains still produce DNS errors; done means the behavior is corrected or clearly explained and stale errors no longer persist.

Written by the indexing model from the issue text.

Assessment

Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.