X-Forwarded-Proto
misconfigured error for IPv6-only visitors when running in Docker through Cloudflared tunnel reverse proxy
#32994
Labels
After upgrading from v7 to v9 we started seeing new errors only when IPv6 visitors try to GET
/user_uploads/.*
URLs on our Zulip server./user_uploads/.*
)(it's possible it happens on other URLs too, but I've only seen errors under that path so far)docker-zulip:9.3
setup on an Ubuntu Digitalocean VPSX-Forwarded-For
,X-Forwarded-Proto
, etc. before sending traffic to the Zulip containerhttps://chat.zulip.org/#narrow/channel/31-production-help/topic/x-forwarded-proto.20in.209.2E3
Config
docker-compose.yml
:etc/zulip/zulip.conf:
Clues
Reverse proxy misconfiguration: No X-Forwarded-Proto header sent from trusted proxy 172.24.0.2
So clearly our
LOADBALANCER_IPS
setting is correct, yet it's claimingX-Forwarded-Proto
header is unset for IPv6 requests, despitecloudflared
100% setting that header before sending traffic to the Zulip Container (verified by swapping out the zulip container with https://github.com/mendhak/docker-http-https-echo and seeing what headers come in).Here are the only clues I've found in the error output:
Full Error Output
Here's a sample of one of the errors (let me know if you want the full text / more error logs from similarly failing requests):
Related Links
zulip/puppet/zulip/templates/nginx/trusted-proto.template.erb
Line 3 in f5f3f12
zulip/puppet/zulip/files/nginx/zulip-include-common/proxy
Line 6 in f5f3f12
zulip/puppet/zulip/files/nginx/uwsgi_params
Line 17 in f5f3f12
Zulip Server and web app version:
*.zulipchat.com
)The text was updated successfully, but these errors were encountered: