acme.json file is not cleaned up
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
To Reproduce
- Create a new project with a valid domain.
- Make sure the HTTPS certificate was generated for that domain.
- Delete the project.
- Go check the acme.json file, and it will still show the old domain from the deleted project.
- Additionally, in 90 days, you'll start to see certificate errors because the domain cannot be verified.
The same thing happens for preview deployments. It appears that as preview deployments are added to the certificate's JSON file, they're not ever cleaned up when previews are removed.
Current vs. Expected behavior
The current behavior causes the Traefik logs to be bloated with additional errors for domains that are no longer being used. Also, this behavior crowds the acme.json file and adds additional bloat to the certificate renewal process.
Provide environment information
OS: Debian 13 (13.6)
Dokploy: v0.29.8 (but recently upgraded to v0.29.13)
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?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the project deletion and preview-removal paths that update Traefik's acme.json state. Reproduce the issue with a generated certificate, then inspect how removed domains are handled. Done means deleted project and preview domains no longer remain in acme.json and renewal errors are no longer produced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100