Cannot use DNS-challenge renewal for server domain
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
My Server is completely private - I cannot use http challenge, currently using DNS challenge for certificate issue and renewal.
Modified Traefik as below for dns-challenge
Been using it for my apps as below
But there isn't an option to define it for Dokploy server domain.
Describe the solution you'd like
Adding custom certificate provider option under server domain section would help define letsencrypt-dns challenge method.
Describe alternatives you've considered
I could not figure out any alternative. Currently using Http challenge, opening port 80 temporary and closing it after renewal.
Additional context
No response
Will you send a PR to implement 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
The issue names no repository files or tests. Start by locating the server-domain certificate configuration and the existing Let's Encrypt challenge settings, then trace how DNS challenge providers are configured for applications. Done means the server domain can use a configurable DNS challenge provider for issuance and renewal without temporarily opening port 80.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100