Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Improve the documentation about putting Zulip behind a reverse proxy
See original GitHub issueHi everyone,
Currently there’s some guidance on how to run Zulip behind a reverse proxy in the documentation, but it appears to be outdated. Starting from #17765 you need to also set the following in zulip.conf; otherwise Zulip thinks all connections come from the reverse proxy itself and IPs are misreported in e.g. “new login” emails.
[loadbalancer]
ips = <ip of the reverse proxy>
Additionally, the guidance to set USE_X_FORWARDED_HOST = True in the Apache section seems to be out of date; this variable is present in the computed settings but I could not find any place in where it is used in the codebase. Maybe it needs to be cleaned from settings as well?
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
USE_X_FORWARDED_HOSTis a core Django setting, which is why it doesn’t show up in the Zulip code. 😃@NexZhu: You can use CIDR ranges when specifying IPs.