Suggest updated prod.env settings for trusted domains and reverse proxy #151
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.
Description:
When deploying wger behind a reverse proxy or Cloudflare Tunnel, Django requires explicit configuration of allowed hosts and CSRF trusted origins.
This PR proposes updating prod.env with recommended settings to prevent common issues such as CSRF errors, redirect loops, or broken HTTPS detection.
Proposed Changes
In production, when using SSL/HTTPS, SITE_URL should be changed to https://yourdomain.com, also - Set DJANGO_ALLOWED_HOSTS and DJANGO_CSRF_TRUSTED_ORIGINS to your real domain with HTTPS.
Benefits:
Ensures correct HTTPS handling behind a reverse proxy or Cloudflare Tunnel
Note: Users must replace yourdomain.com with their actual domain.
Related Issue(s)
See also #134