In Allow self signed certificates · Issue #191 · laurent22/joplin · GitHub, support was added for self-signed certs, but apparently only for Nextcloud. Is there a reason this wasn't added for other sync backends? What would it take to implement this for Joplin Cloud?
@jkaye2012 welcome to the forum.
Could you please clarify what you are asking for? You do not need self-signed certs for Joplin Cloud; Let's Encrypt certs are already set up and as you do not control the Joplin Cloud server you could not use your own self-signed certificates with it anyway.
The ability for the clients to use self-signed certs with Nextcloud was for those people who are hosting their own Nextcloud server and using their own self-signed certificate, rather than one issued by an accredited Certificate Authority.
If you are using a self hosted Joplin Server behind a reverse proxy then you can use self-signed certs or ignore TLS errors using the advanced sync settings, just like you would for a self hosted Nextcloud instance.
Sorry, it seems like I may have misunderstood the Nextcloud portion. Probably a diversion.
My problem is that I'm trying to run Joplin on a network that pushes all TLS traffic through a self-signed certificate enforced by a firewall. This works for most applications, but for some reason it doesn't seem to function with Joplin set up to synchronize with Joplin Cloud (though it was working for e.g. Dropbox). I've tried ignoring certificate errors, but the result is the same - "Failed to fetch".
If there's any way for me to get more useful logs or diagnostics, let me know. I'd be happy to provide them.
I think i workaround is to enable it for Nextcloud and it will apply to Joplin Cloud too
I'll give that a try next week and report back, thank you!
Hey there, unfortunately that doesn't seem to work either. After enabling the cert for Nextcloud, attempting to verify the connection still gives me the same error (SELF_SIGNED_CERT_IN_CHAIN). I did some more digging and attempted to also add the cert in WebDAV, which it looks like might've done something, because now attempting to verify the connection gives a 403 error rather than the cert error, but things are still not working.