-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Federation tester says okay but federation and mail sending fails - OpenSSL/TLS cert CA issue #10976
Comments
Does this possibly have to do with the Let's Encrypt root certificate expiring? |
Hi. Maybe. Letsencrypt has new root cert ISRG root X1. It expired at 30.09. But i already renewed all certs and restarted all services/servers mulitple times. |
This sounds like there's an issue with your setup rather than a bug in Synapse. We only use GitHub issues for bug reports, not for support requests. For support requests, please use the room |
Hi @babolivier, From the output it looks like the root certificate did expire echo quit | openssl s_client -connect matrix.org:443
|
I'm having the same issue as the OP, but I cannot join the #synapse:matrix.org room because my homeserver cannot connect to matrix.org (because of the expired root cert) |
@hasanihunter What version of openssl are you using? This is certainly caused by the DST Root CA X3 Expiration. The default chain recommended by Let's Encrypt retains the expired DST Root CA X3 in order to extend Android device compatibility. As mentioned in the above links, OpenSSL v1.0.x is incompatible with this chain, even when it includes the ISRG Root X1 in its trust store. Can you upgrade to OpenSSL v1.1.x? Further details at https://community.letsencrypt.org/t/openssl-client-compatibility-changes-for-let-s-encrypt-certificates/143816 |
@callahad on a stock M1 mac mini, the version is LibreSSL 2.8.3 and the output on the mac mini is:
On my FreeBSD server, I upgraded to FreeBSD v12.2 and I have OpenSSL 1.1.1 with the output:
While I was able to upgrade my server and openssl library, my concern is that for those that are running a homeserver on the latest version of macOS, they won't be able to federate |
@callahad from the output from both machines in my reply above, it would seem that there are at least two different certificates being presented to a client depending on what version of TLS that the client supports. If that is the case, wouldn't a solution be to update the TLS 1.2 cert to one that is signed by the ISRG Root X1 root? Assuming ISRG Root X1 is in their trust store of course. |
finally the fix was to run that returned "verify error:num=2:unable to get issuer certificate" i removed an old cert file from /etc/ssl/certs and it immediately started to work again |
this won't have fixed anything: it's just a diagnostic. |
it helped me to fix, because it pointed out that the error lies in ssl, not in matrix. i checked the certs on ubuntu server and found out that one of the cert files was obsolete. after removing the statement , |
I know it's not synapse's responsibility to fix SSL issues, but a message indicating -why- a certificate verify failed would be extremely helpful to us in the trenches, and would probably lower the amount of github issues we (mistakenly) file. Some of us are not on the matrix "support" channel. Thank you for at least considering this idea. |
Unfortunately I don't think we get any more information back from the SSL libraries than "validation failed", so it's hard to do much about without rewriting openssl, which sounds... unattractive. |
Hi,
i have serious issue and i dont know how to fix. i invested a lot of time but get no clue about.
https://federationtester.matrix.org/api/report?server_name=matrix.fablabchemnitz.de says our server is fine, but i cannot federate from external matrix servers.
the users on same instance can chat properly.
there is some problem with TLS/SSL and certificate but the cert is fine so far, i think. We use Lets Encrypt
i already posted at closed issue but i started this as a new one because i think its a different issue
related issues are:
postfix log:
the log /var/log/matrix-synapse/homeserver.log says issue about sending mails
and it also says about external room joins:
i checked CA cert which is fine. All things with mail clients work properly, like thunderbird or roundcube or other services which connect to the mail server from exernal or localhost
my mail server only supports TLS 1.2 and TLS 1.3. SSLv2/v3 is completely disabled for smtp/smtpd. I already tried to tie down to TLS 1.0
i updated twisted[tls] und removed the older apt package too python3-twisted
also tried synapse connecting to mail server locally or by public mail server address
some infos about versions:
some more stuff i tried which also looks good, but without solving or modifying the problem:
gives "Verify return code: 2 (unable to get issuer certificate)"
The text was updated successfully, but these errors were encountered: