mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #325] Please add the ability to enable ssl for nginx proxy manager port 81 #285
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#285
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 @marrobHD on GitHub (Mar 13, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/325
Is your feature request related to a problem? Please describe.
All is fine. But I cant get ssl for the nginx proxy manager webinterface working-
Describe the solution you'd like
I want that a option will be added to enable ssl for npm webinterface
Describe alternatives you've considered
I dont know
Additional context
@ShadowPeo commented on GitHub (Mar 18, 2020):
+1 on this, however, to do it with a LetsEncrypt cert you would have to publish it with an external DNS entry which is less than ideal. Combining this with #137 and #313 would be ideal but beggers cannot be choosers
@miguelwill commented on GitHub (Mar 18, 2020):
in my case, I created a proxy_host that derives the connection to port 81, and this way I can use one or several names to get to the dashboard, use ssl custom or let's encrypt, etc
@lopugit commented on GitHub (Mar 25, 2020):
It is a bit weird because it means anyone could sniff your passwords or even login automatically.
I'm just installing now but I'm gonna try add a reverse proxy to npm itself.
ps I just realised that npm stands for nginx proxy manager lol
@miguelwill commented on GitHub (Mar 25, 2020):
hehe, it also happened to me that a few days after using it I realized the meaning of NPM lol.
over the proxy to port 81, I use it that way, and it left 81 only with internal access, and remote access I can achieve using a hostname dedicated to panel access, and with a valid let's encrypt certificate
@lopugit commented on GitHub (Mar 25, 2020):
Ahhh right if you use npm to make the SSL cert then you need a domain I
see. Come on @jc21 we need ip address SSL ;)
On Wed., 25 Mar. 2020, 7:32 pm Miguelwill, notifications@github.com wrote:
@Salvora commented on GitHub (Oct 27, 2020):
+1 for this.
@chaptergy commented on GitHub (May 11, 2021):
Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/182