mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #301] [Feature request] Custom ACME Server URL #266
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#266
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 @asmaps on GitHub (Feb 21, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/301
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
@jc21 commented on GitHub (Feb 24, 2020):
Sounds feasible. I'd be counting on you to test it when required :)
@asmaps commented on GitHub (Feb 26, 2020):
no problem
@github-actions[bot] commented on GitHub (Mar 31, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@jul-fls commented on GitHub (Jul 19, 2024):
Hello, this has been in the pipe for so many time now and it seems to not be very complicated to do as jc21 said 4 years ago.
Would it be possible to have some sort of update about this ?
Btw, thank you very much for this wonderful project that you created !
@github-actions[bot] commented on GitHub (May 10, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@BjoernPetersen commented on GitHub (May 10, 2025):
Not stale
@github-actions[bot] commented on GitHub (Jan 3, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍