mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #944] Use a private CA with certbot for intranet #799
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#799
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 @mkrumbholz on GitHub (Mar 12, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/944
If used as internal reverse proxy it would be great to include auto-renewing certificates on a private CA.
It would need the additional informations:
The CA server URL should also use https and is using a certificate certified with the root certificate of the CA.
Standalone CLI example:
sudo REQUESTS_CA_BUNDLE=path/certs/root_ca.crt certbot certonly -n --standalone -d example.internal --server https://ca.internal/acme/acme/directoryCertbot uses a ENV for the requests CA bundle path.
More examples: https://smallstep.com/docs/tutorials/acme-protocol-acme-clients
@Gitoffomalawn commented on GitHub (Dec 19, 2021):
I'm also interested in this feature. I'm using a private CA for my setup with a non-routable TLD, and having renewal done automatically would be awesome. Looks like integration with SmallStep would make this possible.
@github-actions[bot] commented on GitHub (Mar 17, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 28, 2025):
Issue was closed due to inactivity.
@Gitoffomalawn commented on GitHub (Apr 28, 2025):
Requesting this be reopened, as there's still interest in this feature.