Refactor nginx.conf: clarity, best practices, and correct Cloudflare IP forwarding #19
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.
Summary
This PR refactors the
nginx.conffile for greater clarity, simplicity, and correctness, ensuring proper end-user IP forwarding in a Render.com environment with Cloudflare as a proxy.Details
real_ip_header CF-Connecting-IPwithreal_ip_recursive onfor best Cloudflare/Nginx compatibility.$client_ipto ensure accurate user IP forwarding in headers.locationblock, retaining only necessary proxy configuration..gitignore(exclude temp/cache files and common artifacts).Warning: Task VM test is not passing, Engine will perform much better if you fix the setup