Slavi Pantaleev f0698ee641 Do not overwrite X-Forwarded-For when reverse-proxying to Synapse ... We have a flow like this: 1. matrix.DOMAIN vhost (matrix-domain.conf) 2. matrix-synapse vhost (matrix-synapse.conf); or matrix-corporal container, if enabled 3. (optional) matrix-synapse vhost (matrix-synapse.conf), if matrix-corporal enabled 4. matrix-synapse container We are setting `X-Forwarded-For` correctly in step #1, but were overwriting it in step #2 with something inaccurate. Not doing anything in step #2 is better than doing the wrong thing. It's probably best if we append another reverse-proxy address there though, although what we're doing now (with this patch) seems to yield the correct result (when matrix-corporal is not enabled). When matrix-corporal is enabled, we still seem to do the wrong thing for some reason. It's something to be fixed later on.		2021-03-08 17:24:09 +02:00
..
defaults	Added nginx proxy worker configuration to template and defaults	2021-03-02 11:30:09 +01:00
tasks	Do not delete matrix-ssl-lets-encrypt-certificates-renew only to recreate it later	2021-02-26 13:37:51 +02:00
templates	Do not overwrite X-Forwarded-For when reverse-proxying to Synapse	2021-03-08 17:24:09 +02:00
vars	Replace cronjobs with systemd timers	2021-01-14 23:35:50 +02:00