mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #605] Add self generated certificate as SSL provider #510
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#510
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 @Syam on GitHub (Sep 10, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/605
I am trying to expose some HTTPS services to LAN only.
But when adding a proxy, Nginx Proxy Manager only offer
LetsencryptorNoneas provider.Is it possible to add a self generated certificate as SSL provider ?
Thank,
@chaptergy commented on GitHub (Oct 3, 2020):
When switching to the "SSL Certificates" tab and clicking on the "Add SSL Certificate" button in the upper right corner of the card (Not the big one in the center) you can choose to upload a custom certificate.

This certificate can then be selected for the host.
However it seems since version 2.5.0 the custom certificate upload is broken. See https://github.com/jc21/nginx-proxy-manager/issues/594
@BlackF09 commented on GitHub (Oct 4, 2020):
@chaptergy: I'm unsure if the author meant a third option besides LE an Custom (before step three) like "Own CA". OpenSSL could generate a quick self signed certificate with the given name. I think with this scenario we could even leave out the whole renewal management, just let it generate a new cert eg. after year. Only give the CA certificate to download that it could be added to clients.
Besides that it's a little bit confusing if two buttons with the same name do different things ("Add SSL Certificate").
@jc21 commented on GitHub (Nov 22, 2020):
It was a conscious decision to make the main path for SSL certificate generation use Let's Encrypt because that was the goal of this project. Custom SSL certificates were added by request later in the game.
That said I agree it would be pretty easy to integrate
mkcertinto the project to generate self-signed certs on the fly and then make it part of the Host creation as an option.@chaptergy commented on GitHub (May 12, 2021):
Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/593