NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Load existing LetsEncrypt Cert from volume
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
My problem
I have the problem, that my OPNSense Firewall is already challenging ACME Wildcard Certificate. OPNSense has the ability to transfer the certificates to remote machines with automation. So far, so fine.
With NPM i only have the possibility to upload single certificate files and i need to reupload them over and over again if a new cert from ACME was requested.
I cannot load an existing /etc/letsencrypt folder into NPM. NPM is just ignoring its content and is not giving me an option to use the existing certificate.
My wish
I would like that NPM is recognizing an existing certificate in /etc/letsencrypt and is allowing me use it.
best regards
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 NPM currently discovers and manages certificates when an /etc/letsencrypt volume is present, using the issue's existing-certificate workflow as the entry point. Done means a certificate transferred into that directory can be recognized and selected in NPM without repeated manual uploads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100