[GH-ISSUE #325] Please add the ability to enable ssl for nginx proxy manager port 81 #285

Closed
opened 2026-02-26 06:32:01 +03:00 by kerem · 7 comments
Owner

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

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**
kerem 2026-02-26 06:32:01 +03:00
Author
Owner

@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

<!-- gh-comment-id:600829237 --> @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
Author
Owner

@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

<!-- gh-comment-id:600846887 --> @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
Author
Owner

@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

<!-- gh-comment-id:603641409 --> @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
Author
Owner

@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

<!-- gh-comment-id:603709445 --> @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
Author
Owner

@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:

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


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jc21/nginx-proxy-manager/issues/325#issuecomment-603709445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADH7OBW3OUCIVHAR5JLTQCDRJG6TBANCNFSM4LHCVNPQ
.

<!-- gh-comment-id:603740823 --> @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: > 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 > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/jc21/nginx-proxy-manager/issues/325#issuecomment-603709445>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADH7OBW3OUCIVHAR5JLTQCDRJG6TBANCNFSM4LHCVNPQ> > . >
Author
Owner

@Salvora commented on GitHub (Oct 27, 2020):

+1 for this.

<!-- gh-comment-id:716970006 --> @Salvora commented on GitHub (Oct 27, 2020): +1 for this.
Author
Owner

@chaptergy commented on GitHub (May 11, 2021):

Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/182

<!-- gh-comment-id:839074163 --> @chaptergy commented on GitHub (May 11, 2021): Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/182
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#285
No description provided.