starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #182] Automatic HTTPS redirect for admin access #162

New issue

Closed

opened 2026-02-26 06:31:00 +03:00 by kerem · 9 comments

kerem commented

2026-02-26 06:31:00 +03:00

Owner

Originally created by @pikausp on GitHub (Aug 6, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/182

I was not able to find this in the documentation, but is it possible to acquire SSL cert and proxy traffic to 81 out of the box, or do I need to do that manually when I do not want to access the admin panel via HTTP?

Originally created by @pikausp on GitHub (Aug 6, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/182 I was not able to find this in the documentation, but is it possible to acquire SSL cert and proxy traffic to 81 out of the box, or do I need to do that manually when I do not want to access the admin panel via HTTP?

kerem

2026-02-26 06:31:00 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 06:31:01 +03:00

Author

Owner

@jc21 commented on GitHub (Aug 6, 2019):

What I personally do is use 81 locally at first to create a proxy host for the management interface with ssl enabled. Then I disable docker port forwarding on 81.

@jc21 commented on GitHub (Aug 6, 2019): What I personally do is use 81 locally at first to create a proxy host for the management interface with ssl enabled. Then I disable docker port forwarding on 81.

kerem commented

2026-02-26 06:31:01 +03:00

Author

Owner

@pikausp commented on GitHub (Aug 7, 2019):

@jc21 that's what I did using SSH tunnel, however, I feel like most people will end up accessing the admin panel insecurely over the internet using HTTP, hence the enhancement proposal.

My take is in 95%+ of the scenarios people want/should use 127.0.0.1:81:81 in the ports section and proxy the admin. What do you think?

@pikausp commented on GitHub (Aug 7, 2019): @jc21 that's what I did using SSH tunnel, however, I feel like most people will end up accessing the admin panel insecurely over the internet using HTTP, hence the enhancement proposal. My take is in 95%+ of the scenarios people want/should use `127.0.0.1:81:81` in the `ports` section and proxy the admin. What do you think?

kerem commented

2026-02-26 06:31:01 +03:00

Author

Owner

@DonavanMartin commented on GitHub (Dec 16, 2021):

This issue isn't well documented. Most of users will left 81 port insecure.

@DonavanMartin commented on GitHub (Dec 16, 2021): This issue isn't well documented. Most of users will left 81 port insecure.

kerem commented

2026-02-26 06:31:01 +03:00

Author

Owner

@bbeckford commented on GitHub (Jan 13, 2022):

jc21 What I personally do is use 81 locally at first to create a proxy host for the management interface with ssl enabled. Then I disable docker port forwarding on 81.

Hey @jc21 could you share a quick tutorial on how to set this up?
I've got the proxy working but I want to turn off port 81 publicly now, just not sure how to do that part :)

@bbeckford commented on GitHub (Jan 13, 2022): > [jc21](/jc21) What I personally do is use 81 locally at first to create a proxy host for the management interface with ssl enabled. Then I disable docker port forwarding on 81. Hey @jc21 could you share a quick tutorial on how to set this up? I've got the proxy working but I want to turn off port 81 publicly now, just not sure how to do that part :)

kerem commented

2026-02-26 06:31:02 +03:00

Author

Owner

@jc21 commented on GitHub (Jan 13, 2022):

It's as easy as creating a proxy host to 127.0.0.1 on port 81 and afterwards, updating the docker-compose.yml file to remove port 81 forwarding.

@jc21 commented on GitHub (Jan 13, 2022): It's as easy as creating a proxy host to `127.0.0.1` on port `81` and afterwards, updating the docker-compose.yml file to remove port 81 forwarding.

kerem commented

2026-02-26 06:31:02 +03:00

Author

Owner

@ZeroPing01 commented on GitHub (Mar 12, 2022):

Hey,
@jc21
Thanks for this.
Which certificate do you use for ssl in your lan ?
(is it self signed certificate ?)
I dont want to expose npm web admin on internet.

@ZeroPing01 commented on GitHub (Mar 12, 2022): Hey, @jc21 Thanks for this. Which certificate do you use for ssl in your lan ? (is it self signed certificate ?) I dont want to expose npm web admin on internet.

kerem commented

2026-02-26 06:31:02 +03:00

Author

Owner

@phocks commented on GitHub (Oct 21, 2022):

What I personally do is use 81 locally at first to create a proxy host for the management interface with ssl enabled. Then I disable docker port forwarding on 81.

This is a great idea. Would be good to include in the docs. Cheers!

@phocks commented on GitHub (Oct 21, 2022): > What I personally do is use 81 locally at first to create a proxy host for the management interface with ssl enabled. Then I disable docker port forwarding on 81. This is a great idea. Would be good to include in the docs. Cheers!

kerem commented

2026-02-26 06:31:02 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 2, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Apr 2, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:31:02 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 12, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (May 12, 2025): Issue was closed due to inactivity.

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#162

No description provided.

Rows
Columns