Skip to content

Fix federation for Cloudflare-proxied deployments#6

Open
jevonearth wants to merge 1 commit intoairgap-it:masterfrom
ecadlabs:fix/federation-cloudflare-support
Open

Fix federation for Cloudflare-proxied deployments#6
jevonearth wants to merge 1 commit intoairgap-it:masterfrom
ecadlabs:fix/federation-cloudflare-support

Conversation

@jevonearth
Copy link

Summary

  • Add public_baseurl and serve_server_wellknown: true to homeserver.yaml so Synapse correctly advertises its federation endpoint
  • Add .well-known/matrix/server nginx location block to the readme's example config, which tells remote servers to federate over port 443 instead of 8448

Context

Beacon nodes deployed behind Cloudflare (or any CDN/reverse proxy that doesn't pass through port 8448) fail to federate because remote servers can't discover the correct federation endpoint. These two changes fix that:

  1. serve_server_wellknown makes Synapse serve /.well-known/matrix/server natively
  2. The nginx snippet provides the same discovery at the reverse proxy level, which is needed when Synapse isn't directly exposed

Add public_baseurl and serve_server_wellknown to homeserver.yaml so
Synapse correctly advertises its federation endpoint. Add
.well-known/matrix/server nginx location block to the readme example
config for deployments behind Cloudflare or other CDNs that block
port 8448.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant