mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #49] Self-Signed cert generation #46
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#46
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 @vrelk on GitHub (Jan 12, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/49
Can you add a way to generate a self signed cert and generate/download a CSR? I am using this for some .local addresses as well, so being able to do self signed certs would be nice.
I tried doing this manually and using the Microsoft Cert Authority to make a cert and it failed. I'm not exactly sure why, it just wouldn't upload (upload box wouldn't even close)
@vrelk commented on GitHub (Jan 12, 2019):
Just a note. I generated a CSR on linux machine instead of trying to do it in Windows. (much easier, sorta a derp moment). Anyways, the new cert uploaded fine, so maybe some sort of notification that an error occurred while uploading a cert would be nice, right now it disables the upload button, but nothing else changes.
I would consider this a low priority enhancement, unless someone else sees the need to bump it up. I'm happy for now as I have a cert trusted by Active Directory.
@jc21 commented on GitHub (Jan 14, 2019):
Sounds like a bug verifying the cert on the backend and not handling it. I have tested this with random text files as certs, but I haven't tested with windows generated ones :/
@vrelk commented on GitHub (Jan 14, 2019):
I still have the one I generated. It was a PITA, so I can send it to you if
you want. It's a .local cert, so no security issue, none that I care about
anyways.
On Mon, Jan 14, 2019, 12:13 AM jc21 <notifications@github.com wrote:
@jc21 commented on GitHub (Jan 14, 2019):
In that case, it would be great if you can attach them to this issue :)
@vrelk commented on GitHub (Jan 17, 2019):
Sorry for the delay, but it looks like I deleted it from the network share. If you want I can generate some new ones for you if the other issue that someone opened isn't enough since it appears to be nearly the same problem.
@jc21 commented on GitHub (Feb 18, 2019):
Is this the DES certificates issue? (#52) Anyway, adding yours again for me would be helpful.
@Cassiopeia23 commented on GitHub (Aug 19, 2020):
Hi, I'm also interested in a self signed certificate generator.
I want to use this awesome tool also in my internal network.
What would be the best practice to use my own self signed certificate ?
So I can create one on my own but should I do it within the container our outside and how do I implement it into my configuration ?
@chaptergy commented on GitHub (May 10, 2021):
For all those that come here with this issue: you can't generate a certificate directly in NPM, but instead you have to generate one yourself and upload it as a custom certificate. Use e.g.
opensslfor this. There should be many tools that are able to do this. As a last resort, you can use selfsignedcertificate.com, though it is not recommended since confidential information would be generated on a host of unknown origin.@chaptergy commented on GitHub (May 12, 2021):
Closing in favor of https://github.com/jc21/nginx-proxy-manager/issues/593
root_top.confin the nginx.conf #3754