NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Using cached credentials for dns challenge
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
I am using wildcards and distinct subdomains in npm and using dns challenge to request certificates.
Describe the solution you'd like
Using saved credentials from earlier dns-certificate-challenges for new proxy-hosts i set up.
used credentials already stored in the docker default directory (letsencrypt/credentials/).
Contributor guide
No contributing guide indexed for this repository
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 how DNS certificate challenges currently handle credentials and inspect the Docker default directory at letsencrypt/credentials/. Determine how previously stored credentials could be selected for new proxy hosts without breaking existing challenges. Done means a new proxy host can reuse an earlier DNS challenge credential and the behavior is covered by the relevant tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100