NginxProxyManager / NginxProxyManager/nginx-proxy-manager
[Feature request] Custom ACME Server URL
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.
My home assistant installation is not exposed to the public, so the "classic" let's encrypt does not work. I have a step ca running in my internal network to create self-signed certificates. Step CA now also supports ACME (certbot --server https://ca.internal/acme/acme/directory). It would be awesome to make nginx-proxy-manager use my own CA.
Describe the solution you'd like
Sign certificates via ACME from my own internal ACME server. By adding a config/setting (e.g. per host, per cert or global?) to make certbot use a custom acme server (--server parameter)
Describe alternatives you've considered
Make host public - NO
Create certs manually and add them to nginx-proxy - automating things is better
Additional context
n/a
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 nginx-proxy-manager invokes certbot and how certificate settings are represented. Determine whether the custom ACME server should be configured globally, per host, or per certificate, then verify that certificates can be issued and renewed through the supplied --server URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, typescript
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100