The root CA certificate for Letsencrypt expires today. They have changed to a new provider, but some older systems or libraries do not support it. I am able to browse to my Joplin server that is signed with a Letsencrypt cert, but Joplin reports certificate expired. For reference: https://letsencry…

Same here! I'm using the flatpak version. Joplin 2.4.9.

Luckily, we can temporarily "ignore TLS errors" in the advanced settings under the synchronization section.

Anyone knows how to fix this? Edit: I'm watching this thread and will try to provide a solution as soon as one is available: [Bug]: Let's Encrypt root CA isn't working properly · Issue #31212 · electron/electron · GitHub

This was driving me absolutely nuts until I found out that many people are running into this same issue. If I understand right something in Joplin needs to be changed to correct this? Or does my admin need to fix something on the server side?

Something will need to be fixed on the app but it's unclear what at this point. In the meantime you should be able to fix the server using this method: [Bug]: Let's Encrypt root CA isn't working properly · Issue #31212 · electron/electron · GitHub

looks like they have a proposed fix fix: Enable X509_V_FLAG_TRUSTED_FIRST flag in BoringSSL committed 05:43PM - 30 Sep 21 UTC (UTC) [jviotti] jviotti +2…

I think there's an unfortunate chance that this might only end up applied to the actively supported Electron versions, (13, 14, 15). Since this problem effectively breaks every Electron version prior, I doubt they'd rebuild earlier releases because there has to be a line drawn somewhere (there's peo…

looks like it's only a few lines of code for the fix if that is the verified fix couldn't someone just backport it into the older version of electron?

The backporting might be fairly trivial, but the build process for Electron takes hours to days even on dedicated machinery, combined with multiple versions and multiple architectures, I doubt Microsoft would bother with anything that isn't officially supported still. npm doesn't build Electron, it…

okay so it sounds like fix it on the backend because the app may be fixed basically never.

Letsencrypt root CA certificate expiration

Support

Topic		Replies	Views
Fix for "Certificate has expired" error with Joplin Cloud and self-hosted sync targets News	22	11312	9 October 2021
Sync to Nextcloud (Linux Ubuntu 20.04) Support	4	732	27 November 2021
Certificate Error since upgrading to 2.4.9 on Windows Support	1	960	4 October 2021
Joplin Server Syncing Failed - Cert Expired - HAProxy Support	1	1288	1 October 2021
Self signed certificate errors while sync and plugin install Features	1	182	21 August 2025

Letsencrypt root CA certificate expiration

Related topics