3 ms·
I couldn't get it working with a self-signed certificate and I'm now forced to use a let's encrypt certificate, although the server is not public facing.
by janwillemb 6y ago
I couldn't get it working with a self-signed certificate and I'm now forced to use a let's encrypt certificate, although the server is not public facing.
- throwanem 6y agoTry adding the root CA cert you created to sign the self-signed cert to whatever certificate trust store Thunderbird uses on your system, maybe? It's been a while since I had to deal with this on any OS so I can't give specific advice on how to do it, but generally my experience has been that this is a good first step in resolving trust failures with self-signed certificates.
- janwillemb 6y agoI tried that (I've done this many times because of local development of APIs), but Thunderbird doesn't seem to use this. Or: it is another problem, but Thunderbird doesn't give any helpful message.
- throwanem 6y agoAh, it looks like Tbird uses its own cert store, maybe. https://manuals.gfi.com/en/kerio/connect/content/server-configuration/ssl-certificates/self-signed-certificates-in-mozilla-thunderbird-950.html https://manuals.gfi.com/en/kerio/connect/content/server-conf... describes a pretty unique process for manually applying a trust exception to an arbitrary server cert - maybe worth a try if you didn't know about it, as I also did not until five minutes ago despite having used Thunderbird for what must now be a couple of decades.