From 23783f87bcdc4429a609f82be9d6682c5918fb94 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 15 Jul 2026 13:30:45 +0300 Subject: [PATCH] Clarify when disabling the federation port applies in the CDN guide The CDN section of the federation documentation tells users to set matrix_synapse_federation_port_enabled: false, which only works because that recipe moves federation traffic to the client port. Followed partially (keeping federation on the dedicated federation port behind a fronting reverse proxy), the same line removes the federation route entirely and breaks federation. Say so explicitly. Fixes #4475 Co-Authored-By: Claude Fable 5 --- docs/configuring-playbook-federation.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/configuring-playbook-federation.md b/docs/configuring-playbook-federation.md index 560c241e0..a92a67ce6 100644 --- a/docs/configuring-playbook-federation.md +++ b/docs/configuring-playbook-federation.md @@ -71,4 +71,6 @@ matrix_synapse_federation_port_enabled: false matrix_synapse_tls_federation_listener_enabled: false ``` +**Note**: `matrix_synapse_federation_port_enabled: false` only makes sense in this specific setup, where federation traffic is served through the client port (because of the `federation` entry in `matrix_synapse_http_listener_resource_names`). If federation still flows through the dedicated federation port on your setup (e.g. another reverse proxy of yours forwarding a custom public port to this playbook's federation port), leave `matrix_synapse_federation_port_enabled` at its default (enabled). Disabling it removes the federation route entirely and breaks such setups. + **Use this at you own risk as all the possible side-effects of doing this are not fully known. However, it has been tested and works fine and passes all the tests on without issues.**