You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Slavi Pantaleev 3a5f82267b Do not use Let's Encrypt certificate for Synapse's federation port ... As described here ( https://github.com/matrix-org/synapse/issues/2438#issuecomment-327424711 ), using own SSL certificates for the federation port is more fragile, as renewing them could cause federation outages. The recommended setup is to use the self-signed certificates generated by Synapse. On the 443 port (matrix-nginx-proxy) side, we still use the Let's Encrypt certificates, which ensures API consumers work without having to trust "our own CA". Having done this, we also don't need to ever restart Synapse anymore, as no new SSL certificates need to be applied there. It's just matrix-nginx-proxy that needs to be restarted, and it doesn't even need a full restart as an "nginx reload" does the job of swithing to the new SSL certificates.		7 years ago
..
matrix-nginx-proxy.service.j2	Do not use Let's Encrypt certificate for Synapse's federation port	7 years ago
matrix-postgres.service.j2	Initial commit	7 years ago
matrix-riot-web.service.j2	Add support for not taking over a server (no matrix-nginx-proxy) and disabling Riot	7 years ago
matrix-s3fs.service.j2	Add support for storing Matrix Synapse's media_store to Amazon S3	7 years ago
matrix-synapse.service.j2	Do not use Let's Encrypt certificate for Synapse's federation port	7 years ago