feat: trust Sucuri's IP Addresses on nginx #595
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It would be nice if this could be made easily configurable for any upstream ranges I want. |
|
This is already configurable by mounting an additional .conf file, which is what I'm doing currently |
|
I already feel that the trust is too wide. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Siimilar to Cloudflare, Sucuri is a popular proxy/firewall service provider. This PR adds their trusted/secured ips for the nginx images
Found here under the 502:
https://docs.sucuri.net/website-firewall/sucuri-firewall-troubleshooting-guide/