matrix-docker-ansible-deploy/roles/matrix-server/templates/cron.d/matrix-nginx-proxy-periodic-restarter.j2

MAILTO="{{ matrix_ssl_lets_encrypt_support_email }}"

# This periodically reloads the matrix-nginx-proxy service
# to ensure it's using the latest SSL certificate
# in case it got renewed by the `matrix-ssl-certificate-renewal` cronjob
# (which happens once every ~2-3 months).

{{ matrix_nginx_proxy_reload_cron_time_definition }} root /usr/bin/systemctl reload matrix-nginx-proxy.service
Add support for 2 more SSL certificate retrieval methods Adds support for managing certificates manually and for having the playbook generate self-signed certificates for you. With this, Let's Encrypt usage is no longer required. Fixes Github issue #50. 2018-12-23 09:00:12 +00:00			`MAILTO="{{ matrix_ssl_lets_encrypt_support_email }}"`
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. 2017-09-23 12:08:54 +00:00
			`# This periodically reloads the matrix-nginx-proxy service`
			`# to ensure it's using the latest SSL certificate`
			# in case it got renewed by the `matrix-ssl-certificate-renewal` cronjob
			`# (which happens once every ~2-3 months).`

			`{{ matrix_nginx_proxy_reload_cron_time_definition }} root /usr/bin/systemctl reload matrix-nginx-proxy.service`