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.
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?
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 people saying this effects Electron 8 that they're still actively using for example).
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 downloads pre-compiled binaries. Building it just takes forever.
For example, setting up Chromium on ARM64 takes Ubuntu/Canonical 3 days.
I'm really hoping they'll consider backporting the fix because it's a major problem for thousands of apps out there, and many of these can't easily upgrade Electron.
Ok looks like they'll only backport to v12 and we're on v10. There's a version that's no good for us due to sandbox changes but I forgot which one (maybe v13? ) . Hopefully we can at least upgrade to v12 without too much trouble.
I have the same issue with Joplin on my Windows. I was able to fix the Chrome having issues with LE sites by installing their root cert into the Windows cert store but Joplin (also guessing all other Electron apps) do not accept that solution.
) . Hopefully we can at least upgrade to v12 without too much trouble.