yes sorry I meant to get back to my post. When I tried on my linux machine, the client I was using wasn't updated at the latest version! After the update to the latest version I got the error too!
1 Like
Maybe it's true, but it doesn't work for me. I updated the letsencrypt certificate for Nextcloud a few days ago. I have the status
Start Time: 1633547635
Timeout: 7200 (sec)
Verify return code: 0 (ok)
Extended master secret: no
Max Early Date: 0
and the desktop client still shows me sync errors
EDIT. the joplin mobile app syncs without any problem
after many attempts on the server it turned out that it is enough to install the new version of joplin 2.5.1
The only question is whether the joplin itself changes something or it was enough to do a reinstall.
It is Electron that was the issue. 2.5 upgraded the framework.