search

spantaleev / matrix-docker-ansible-deploy

🐳 Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
GNU Affero General Public License v3.0
4.74k stars 1.02k forks source link

Synapse Workers with Sliding Sync resulting in broken Client API #3429

Open throny opened 1 month ago

throny commented 1 month ago

Describe the bug When having a setup with either specialized or generic workers, the client API endpoint seems to fail. I did not test with federation-only workers yet, but I guess, they should work.

I tried to include all relevant config entries. Let me know, if there's something missing, but my yml is quite extensive. To Reproduce

matrix_synapse_workers_enabled: true
matrix_synapse_workers_preset: specialized-workers
matrix_sliding_sync_enabled: true 
matrix_playbook_reverse_proxy_type: other-traefik-container
matrix_playbook_reverse_proxy_hostname: traefik
devture_traefik_certs_dumper_ssl_dir_path: "/containers/traefik/letsencrypt"
matrix_federation_traefik_entrypoint_name: web-secure
matrix_static_files_container_labels_base_domain_enabled: true
# change federation to 443
matrix_synapse_http_listener_resource_names: ["client","federation","openid"]
matrix_federation_public_port: 443
matrix_synapse_federation_port_enabled: false

Expected behavior A running Sliding Sync proxy with workers enabled.

Matrix Server:

Additional context If you agree that this might be a bug, I already adjusted the documentation in my PR

spantaleev commented 1 month ago

I think plenty of people are running sliding-syn in combination with Synapse workers, so the problem is probably not very frequently occurring.

You're changing quite a bit in your configuration, so I suspect it's got something to do with that.