mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #137] Add IP based access lists #119
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#119
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 @joeldevnull on GitHub (May 6, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/137
Hi,
Thanks for creating an awesome tool for managing nginx proxy configs.
Is it possible to consider adding IP based restrictions to the access lists? This is relatively simple to implement in nginx itself in the location block and can be mixed with the existing auth basic too, e.g:
Thanks again!
@jeliasson commented on GitHub (May 30, 2019):
Yes, this is the only thing I'm missing right now. Great tool!
@axipher commented on GitHub (Jun 28, 2019):
I would also love a feature like this so I don't have to install additional Dockers to handle access control, limit external access to certain IP's and even limit internal network traffic as well.
@arejaytee commented on GitHub (Jan 26, 2020):
+1 for this feature to be added
@michaelruge commented on GitHub (Feb 1, 2020):
I too would love to see this feature!
@modem7 commented on GitHub (Mar 9, 2020):
This can already be used quite easily?
Downside is the basic auth doesn't work to well unless you manually do it.
@arejaytee commented on GitHub (Mar 9, 2020):
Yeah I was going to give it a try with doing it manually, plan was to do it with no auth and have the IP restriction do the work.
@arejaytee commented on GitHub (Mar 10, 2020):
Confirmed the settings below will work for IP based restrictions, you can place it in the Host advanced settings or individually for each location. Getting redirected to a 403 page which would be nice to be able to customise or by default use the same Tabler theme.
Being able to configure an "Advanced Access list" with settings like below would be great for displaying it within the UI nicely.
#Settings
#localhost
allow 127.0.0.1;
#local internal network
allow 192.168.1.0/24;
#external IP Address
allow 158.140.198.146;
#deny everything except the above
deny all;
@jc21 commented on GitHub (May 29, 2020):
Feature has been added, closing
@johanmorenolds commented on GitHub (May 6, 2021):
thanks a lot, i just started using the tool and is it great!, and besides that the community is super supportive and active i was having some troubles trying to restrict access to certain IP addresses and with the community help i just managed.
thanks @arejaytee for the code: