-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
Create internal.conf #520
Create internal.conf #520
Conversation
Add a single conf file that can be used in proxy-confs via "include /config/nginx/internal.conf" for a single point of management for allowed IPs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for opening this pull request! Be sure to follow the pull request template!
Changed from explicit IP ranges to using an included config file. Recommend this shouldn't be merged upstream unless linuxserver/docker-swag#520 is as well. Signed-off-by: hellblazer315 <[email protected]>
I am a bot, here are the test results for this PR:
|
I am a bot, here is the pushed image/manifest for this PR:
|
I am a bot, here is the pushed image/manifest for this PR:
|
I am not seeing any value here. Many users create an allowdeny.conf or internal.conf to use as they see fit, but prepopulating ip ranges, especially external ones in a file named internal.conf just seems odd to me. Yes, i understand the reason you put tailscale ips in there, no it doesnt make them internal ips. this type of change is best left up to the individual users to handle. with that said, thank you for your effort in creating this PR, filling out the template appropriately, and sharing your code with us! |
Add a single conf file that can be used in proxy-confs via "include /config/nginx/internal.conf" for a single point of management for allowed IPs.
EDIT: Completed template.
Description:
Added an internal.conf that specifies common internal IP ranges and tailscale's default range. Blocks access from all other IPs with a 403.
Benefits of this PR and context:
Provides a single place to specify approved IP ranges that may be used across multiple proxy-confs via "include /config/nginx/internal.conf".
How Has This Been Tested?
Yes, had the same snippet within the file in my dashboard.subdomain.conf. Removed that in exchange for "include /config/nginx/internal.conf" and access is still restricted to local IPs.
Source / References:
N/A