-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Federation was broken between my homeserver and matrix.org (and I fixed it with this patch) #14492
Comments
[The mentioned admin speaking] The dying endpoint was |
We also ran into this issue, but not with Synapse limiting the request size to |
It turned out that my issue was more or less "user error", as matrix-docker-ansible-deploy allows 150 MB for federation requests in the default, recommended configuration (which I didn't use). But I wonder if Synapse is supposed to make federation requests that are bigger than 50 megabytes, or if there is some kind of bug somewhere. |
The latter. Thanks for the report, everyone---we'll investigate. |
@davidmehren I didn't comment because you repeated what I just wrote about reverse proxy limit, but since you've mentioned "it was an user error" in #14513 I wanted to say that no, it wasn't. Sane reverse proxy limit is not an user error in general, regardless of whether in your case you and docker would have used a different limit (since it would have been hitting as well, maybe later). @DMRobertson if you need any info (since we have seen both the source and the events) contact me [@grin:grin.hu], I'd rather not put the details it here. |
I'm having this issue too |
@Cknight70 What is your homeserver's address? If you don't want to share publicly, I'm reachable at @DMRobertson:matrix.org |
Thanks everyone for reporting, and apologies for a delay in an update to this issue.
There definitely was a bug. See GHSA-f3wc-3vxv-xmvr for details; the fix was in #14642. |
Description
federation between my homeserver and matrix.org was broken. My homeserver was able to send messages but messages sent from matrix.org were never received. I was not the only server affected by this issue and another homeserver admin found a solution in #synapse-admins:
This patch worked for the original author and I confirm it is working for me too. I also made sure the parameter
client_max_body_size
in my nginx reverse-proxy was high enough. Increasing the value in nginx was not enough to fix the issue, the patch above was needed. I was affected by this bug since last weekend and I did a lot of tests by changing many values in nginx by increasing timeouts and size but nothing worked. I also tried changing synapse cache values and configs but that didn't do the trick either.Steps to reproduce
I do not know how to reproduce the initial conditions that caused the bug but the patch fixed the federation between my server and matrix.org.
Homeserver
matrix.org was the server unable to send messages
Synapse Version
1.72.0rc1 for matrix and I run 1.71.0
Installation Method
Docker (matrixdotorg/synapse)
Platform
Ubuntu LTS and I use the Ansible playbook from https://github.com/spantaleev/matrix-docker-ansible-deploy
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: