You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
When using certbot to generate certificates, it generates the following files:
root@errol:~# ls /etc/letsencrypt/live/chat.abolivier.bzh/
cert.pem chain.pem fullchain.pem privkey.pem README
root@errol:~#
Since the Synapse docs don't say anything about which one to use, and the relevant config option is named tls_certificate_path, people might tell Synapse to use cert.pem whereas it should be using fullchain.pem, which contains the complete certificate chain. This will likely prevent these people from federating once we start enforcing valid certs.
The text was updated successfully, but these errors were encountered:
Yes, my issue was very specific to certbot (thought it would be useful for context), but a simple note of "use the full chain, not just the cert" would be helpful
babolivier
changed the title
Tell people to use "fullchain.pem" instead of "cert.pem" when using synapse with certbot
Tell people to give synapse the full certificate chain, not just the single certificate
Feb 28, 2019
When using certbot to generate certificates, it generates the following files:
Since the Synapse docs don't say anything about which one to use, and the relevant config option is named
tls_certificate_path
, people might tell Synapse to usecert.pem
whereas it should be usingfullchain.pem
, which contains the complete certificate chain. This will likely prevent these people from federating once we start enforcing valid certs.The text was updated successfully, but these errors were encountered: