Skip to content
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

Closed
wants to merge 1 commit into from
Closed

Conversation

hellblazer315
Copy link

@hellblazer315 hellblazer315 commented Nov 11, 2024

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.

linuxserver.io


  • I have read the contributing guideline and understand that I have made the correct modifications

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

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.
Copy link

@github-actions github-actions bot left a 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!

hellblazer315 added a commit to hellblazer315/docker-mods that referenced this pull request Nov 11, 2024
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]>
@LinuxServer-CI
Copy link
Contributor

I am a bot, here are the test results for this PR:
https://ci-tests.linuxserver.io/lspipepr/swag/3.0.0-pkg-2b1e4736-dev-712c6f64b5c70ce2bdffc60d25d465e9d246903e-pr-520/index.html
https://ci-tests.linuxserver.io/lspipepr/swag/3.0.0-pkg-2b1e4736-dev-712c6f64b5c70ce2bdffc60d25d465e9d246903e-pr-520/shellcheck-result.xml

Tag Passed
amd64-3.0.0-pkg-2b1e4736-dev-712c6f64b5c70ce2bdffc60d25d465e9d246903e-pr-520
arm64v8-3.0.0-pkg-2b1e4736-dev-712c6f64b5c70ce2bdffc60d25d465e9d246903e-pr-520

@LinuxServer-CI
Copy link
Contributor

I am a bot, here is the pushed image/manifest for this PR:

ghcr.io/linuxserver/lspipepr-swag:3.0.1-pkg-9005d62d-dev-691ab0008ee247255bdd8f80277d4a09c9b1eb61-pr-520

@LinuxServer-CI
Copy link
Contributor

I am a bot, here is the pushed image/manifest for this PR:

ghcr.io/linuxserver/lspipepr-swag:3.0.1-pkg-dc9e7754-dev-288425a43cff86567c30b118a4ba1434eea223c7-pr-520

@drizuid
Copy link
Member

drizuid commented Jan 10, 2025

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!

@drizuid drizuid closed this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

3 participants