mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #440] Guide for setting up access lists? #370
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#370
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 @ghost on GitHub (Jun 1, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/440
Checklist
What is troubling you?
Is there a clear guide on how to set up access lists? I'd just like to require a username and password to gain access to one of my proxy hosts (no IP addresses or ranges), but I can't figure out how to do it when playing around with it.
@denisjoshua commented on GitHub (Jun 14, 2020):
I need this access list also
Thanks a lot
@denisjoshua commented on GitHub (Jun 15, 2020):
Now I find it on the web page menu :-)
Thanks
@N4v41 commented on GitHub (Jul 2, 2020):
hi, i've got some problems to understand how access lists function in npm, but basically you create an acess list, under details you put the name of the list and tell if it will be satisfied by any requirements or 2 of them user/password and iprestiction, into the authorization tab you create the basic auth users and passwords, in Acess you specify a directive bypass(if satisfies any was toggled)/restict the auth by ip or network.
i have noted that after you change the access list you have to remove and put again in the proxy host so the update will be effective.
@5hay commented on GitHub (Mar 9, 2021):
Thanks, I was wondering why there was no change. This is still the case.
@github-actions[bot] commented on GitHub (Mar 28, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 8, 2025):
Issue was closed due to inactivity.