mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-28 10:55:54 +03:00
[GH-ISSUE #2984] Add more options for certificate sources #2032
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2032
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @minecrawler on GitHub (Jun 6, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2984
Is your feature request related to a problem? Please describe.
Currently, NPM supports Let's Encrypt or uploading custom certificates. As a self-hoster, all my services are internal, so Let's Encrypt doesn't work. Creating a custom certificate for each service is tedious. I wish there were better options in NPM for self-hosters!
Describe the solution you'd like
NPM should support configuring the ACME server, so that I can setup a Smallstep or Boulder CA server myself (e.g. direct it to
https://my-ca.localfor certificate requests)Describe alternatives you've considered
Additional context
should become
The "several custom CAs" thing is just an idea, though practically most people probably only have one... as long as it remembers the info for that one I don't care if there's only one option :)
Also, the rename of "Custom" felt better with all the new options, but I have no strong feelings about it...
@Catospye commented on GitHub (Jun 7, 2023):
bump!
@github-actions[bot] commented on GitHub (Jan 18, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@minecrawler commented on GitHub (Jan 18, 2024):
Still very much relevant!
@Gauss23 commented on GitHub (Apr 15, 2024):
I think this is a really nice feature.
@github-actions[bot] commented on GitHub (Nov 7, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Gauss23 commented on GitHub (Nov 7, 2024):
👍
@minecrawler commented on GitHub (Nov 7, 2024):
still labelled as stale, so another bump for the bot
@minecrawler commented on GitHub (Nov 7, 2024):
@jc21 is there any process which needs to be triggered? Or is it just a "I don't have time right now, no one else is working on it, and you should just do it yourself" situation?
@TiggsPanther commented on GitHub (Jan 20, 2025):
I'll add another vote to this one.
I've started using step-ca so I can automate internal certs for my environment. Being able to specify that in NPM would be useful in that.
@github-actions[bot] commented on GitHub (Aug 11, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@minecrawler commented on GitHub (Aug 12, 2025):
still relevant
@danieltr3s commented on GitHub (Aug 15, 2025):
bump!
@LeMathochist commented on GitHub (Jan 1, 2026):
Bump bump bump. Would like option to chose source CA.