mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #5193] Support custom / internal ACME CA using HTTP-01 challenge #3136
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#3136
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 @vsc55 on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5193
Is your feature request related to a problem? Please describe.
Nginx Proxy Manager only supports Let’s Encrypt as an ACME provider and does not allow configuring a custom ACME directory URL.
This prevents using NPM with an internal or private ACME CA, even when the CA supports the standard HTTP-01 challenge.
Describe the solution you'd like
Add support for a custom / internal ACME CA with:
Describe alternatives you've considered
Additional context
This would enable fully automated certificate management in homelab and private environments without relying on Let’s Encrypt.