-
Notifications
You must be signed in to change notification settings - Fork 3k
Add IP based access lists #137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes, this is the only thing I'm missing right now. Great tool! |
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. |
+1 for this feature to be added |
I too would love to see this feature! |
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. |
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 #local internal network #external IP Address #deny everything except the above |
Feature has been added, closing |
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:
|
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!
The text was updated successfully, but these errors were encountered: