I am on win10.
Using Joplin open source note taking app, set up to sync with Nextcloud folder through webdav. Joplin syncs on its own. No Nextcloud client involved.
It has worked perfectly since installation, for over 6 months. 4 days ago the Win10 computer stopped syncing. For a couple of days there was no error message. Now I get the following error message in Joplin:
request to “https://mia.nl.tab.digital/remote.php/dav/files/astro46%40fastmail.fm/Joplin/ failed, reason: write EPROTO 615680:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:....\third_party\boringssl\src\ssl\tls_record.cc:130: (Code EPROTO)”.
I have no idea what this error message means.
I also have Joplin on iphone 6s. I am not getting any sync errors on iphone.
I have checked the username/password and webdav url. See no problems there. I haven’t changed any settings recently.
Anyone have an idea what has happened; Why did sync stop working?
Yeah, but even if changing the URL to HTTP would work it’s, of course, not an actual solution, for obvious reasons.
It also likely means that the server isn’t configured correctly for HTTPS, and since tab.digital is a managed Nextcloud provider, I would contact them to find a solution.
http with or without ‘s’ makes no difference. not does syncing through the joplin webdav configuration, as opposed to the normal joplin nextcloud config. Since nothing changed on my end, including not having updated joplin right before the failure, best guess is that this is a nextcloud failure.
best would be for someone from nextcloud to comment here about changes to their login .
I cannot fully agree to this assumption, because Nextcloud is a software which runs on top of your existing OS. If changes are brought in by the OS, Nextcloud isn’t responsible for it.
Due to the fact that a clear OpenSSL error message is show I would assume that OpenSSL changed its behavior because e.g. it defaults to TLS v1.1 and higher etc. (as far as I remember previous protocols have been disabled by default) You find a lot of related messages on the internet.
Nextcloud doesn’t handle TLS itself, it’s handled by the web server and the operating system. As @j-ed mentioned, the issue is most likely rooted there.
Ultimately, though, it doesn’t make much difference in your case because tab.digital manages all of it, including Nextcloud. Only they can investigate further or make any necessary changes. So once again, contacting their support is probably your best chance of finding a solution.
In theory, although I’d say less likely, it could also be a client-side issue or a combination of client and server. To rule this out, make sure your operating system is up to date and that you’re using the latest version of the Joplin client. It may also be worth checking the Joplin Forum and their issue tracker for similar reports.
I returned home last night and found that Joplin is syncing ok to the two computers at home, and the laptop that I was traveling with is now also syncing. No error messages. All is working normally.
I don’t know how to explain this. When in the other location my iphone didn’t give error but laptop did and data was not syncing between the two. both connected to same network.
I have tried joplin sync, using dropbox, on a wifi network that previously failed when using nextcloud. Worked fine. Can’t try it on the first wi-fi network that failed when syncing through nextcloud, since it is halfway across the country. At this point it seems that the syncing issue is resolved, and it is logical to assume that it is nextcloud related. time will tell.
