Artur Neumann

@reetp you are right, I've updated the original comment to 1. set the tag to `6.12.0` and not to `latest` 2. confirm that `6.11.2` works correctly I've tried every major...

Digging deeper, Rocket.Chat 6.12 started to send pings to the homeserver to verify the configuration is correct, see https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/server/services/federation/service.ts#L290 synapse seem to have a bug in the version that is...

I also could make it work in both directions with synapse 1.71 and rocket.chat 6.11.2 RC 6.11.2 does not work with newer versions of synapse (tried 1.89, 1.114), I believe...

One more observation: never versions of synapse using the `Authorization` header as described in https://spec.matrix.org/v1.11/application-service-api/#authorization ,but Rocket.Chat expects (as far as I can see) uses the token in a query...

I might have been wrong about the legacy routes, the federation mostly works for me now after setting `use_appservice_legacy_authorization: true` in `homeserver.yaml`

As mentioned above (by my and @IvanOtkidach), the magic fix seems to be to set `use_appservice_legacy_authorization: true` At the time when I found the solution and wrote my last message...

@ItaloCobains did you change the length directly in the DB or where?

my debugging shows that the code really arrives in https://github.com/owncloud/core/blob/e60f5f03dcf0f23cba622d4343579e3d3f2ee970/lib/private/Files/Storage/Local.php#L298 and `fopen` gets all the right data but returns `false` I can see the data on disk and can read...