Enhance Nginx reverse proxy configurations for HTTP/3 and SOGo #904
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.
This commit updates the documentation to provide crucial configuration adjustments for Nginx reverse proxies utilizing HTTP/3, specifically addressing SOGo redirect issues within Mailcow.
Two key nginx areas are covered:
reuseportDirective Management:The
reuseportdirective, while useful for opening UDP port on the same as the TCP port on a virtual server instance, should only be used once (like always withdefault_server) when used in HTTP/3 configurations. Disablingreuseportexcept for one occurrence has resolved issues where nginx reports errors...: duplicate listen options for 0.0.0.0:443 in /etc/nginx/....Correct Host Resolution for SOGo Redirects:
After a successful login, SOGo issues 302 temporary redirects to the user's mailbox. With HTTP/3, the
proxy_set_header Host $http_host;directive result in SOGo generating redirects with an incorrect or missing hostname (e.g.,https:///SOGo/...). Switching toproxy_set_header Host $host;ensures the correct hostname is passed to SOGo, allowing it to construct accurate redirect URLs.These clarifications will help users configure their Nginx reverse proxies to maintain seamless SOGo functionality when enabling HTTP/3.