starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #1880] How-to "Basic HTTP Auth" protect the NPM admin portal? #1373

New issue

Closed

opened 2026-02-26 07:30:43 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:30:43 +03:00

Owner

Originally created by @ctrlbrk42 on GitHub (Feb 22, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1880

My NPM is public internet facing, and it would make me sleep better at night if I could simply implement HTTP Basic Auth for the NPM admin portal itself, but it doesn't seem supported.

Originally created by @ctrlbrk42 on GitHub (Feb 22, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1880 My NPM is public internet facing, and it would make me sleep better at night if I could simply implement HTTP Basic Auth for the NPM admin portal itself, but it doesn't seem supported.

kerem

2026-02-26 07:30:43 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 07:30:43 +03:00

Author

Owner

@caesartcs commented on GitHub (Apr 16, 2022):

So generally speaking, you don't want to expose port 81 to the public internet, just 80, 443. Ideally, good security practice would be to leave it internal and perhaps use a VPN to get into your network and access it that way.

If you are trying to remotely access your NPM dashboard from the internet, 2FA is another option and might be implemented in v3 (#1202). But there is potentially a way to do that today.

If you have your NPM proxy dashboard (I mean port 81) as a subdomain (which come to think of it, idk if you can. I think you should be able to), I would suggest you spin up Authelia and run through this guide https://thehomelab.wiki/books/dns-reverse-proxy/page/setup-authelia-to-work-with-nginx-proxy-manager

@caesartcs commented on GitHub (Apr 16, 2022): **So generally speaking, you don't want to expose `port 81` to the public internet, just `80, 443`.** Ideally, good security practice would be to leave it internal and perhaps use a VPN to get into your network and access it that way. If you are trying to remotely access your NPM dashboard from the internet, 2FA is another option and might be implemented in v3 (#1202). But there is potentially a way to do that today. If you have your NPM proxy dashboard (I mean `port 81`) as a subdomain (which come to think of it, idk if you can. I think you should be able to), I would suggest you spin up [Authelia](https://www.authelia.com/) and run through this guide [https://thehomelab.wiki/books/dns-reverse-proxy/page/setup-authelia-to-work-with-nginx-proxy-manager](https://thehomelab.wiki/books/dns-reverse-proxy/page/setup-authelia-to-work-with-nginx-proxy-manager)

kerem commented

2026-02-26 07:30:43 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 23, 2024):

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

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

kerem commented

2026-02-26 07:30:44 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 8, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 8, 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#1373

No description provided.

Rows
Columns