Fixes #901 - Explain NGINX_SERVER_SCHEME in the HTTPS scenarios - #903
Merged
Merged
Conversation
The scenarios that terminate TLS at a reverse proxy set NGINX_SERVER_SCHEME=https themselves since zammad-docker-compose#614. Document why on the scenarios page: Zammad's bundled Nginx overwrites X-Forwarded-Proto, so the scheme must be configured in Zammad's own Nginx or the 'Secure' session cookie is never written and login fails with a CSRF token verification error. Related issue: #901
ArtifactsProduced during runtime |
dvuckovic
approved these changes
Sep 8, 2026
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
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.
The scenarios that terminate TLS at a reverse proxy set NGINX_SERVER_SCHEME=https themselves since zammad-docker-compose#614. Document why on the scenarios page: Zammad's bundled Nginx overwrites X-Forwarded-Proto, so the scheme must be configured in Zammad's own Nginx or the 'Secure' session cookie is never written and login fails with a CSRF token verification error.
Related issue: #901