sync with nextcloud stopped working a couple of days ago. I see one other thread about nextcloud mysteriously encrypting files from this past april, but nothing else.
Is anyone still using nextcloud (Tab) successfully for syncing?
yes, I am. I am syncing my desktop Joplin (MacOS) to a folder within my Nextcloud folder and let the Nextcloud client do the uploading/downloading.
On my iPad and iPhone, I have configured Joplin to use WebDAV as sync target and pointed it to my Nextcloud. Everything works totally fine.
Server sided encryption is enabled in my Nextcloud, so that shouldn't be a problem. Have you tried re-setting up your sync via Nextcloud?
i have written nextcloud forum. I'll find out if any useful info is given.
in the meantime, if I should decide to try using nextcloud client from win10:
what folder/files should I tell nextcloud client to sync to nextcloud joplin folder?
I am guessing the joplin files/folder needs to be in a nextcloud sync folder: how do I tell joplin that it will use that location in the future?
Huh? This is exactly the problem. As referred in my first post, and referred to a different thread seeking a possible solution, the Joplin sync to Nextcloud has failed since 4 days ago. It is no longer working for me. This is why I started this thread.
Fair enough. I sort of fixated on your last post and forgot the point you made in your first post.
It is a while since I used a Nextcloud server for sync but an option is to try the WebDAV sync connector option rather than the Nextcloud one. I used to use that when I had a Nextcloud server as I found it more reliable. Of course this is unlikely to work if Tab Digital have done something that causes the OpenSSL mismatch between client and server. (Your other post).
The other option is, as you say, to try to use the Nextcloud client (assuming it does not also suffer the same error) to do the work instead. In that case you use file system sync to point Joplin to the folder being synced by the Nextcloud client.
Interesting idea, though don't know the details of what it means. I did try setting Joplin sync to Webdav, using the Nextcloud url , un/pw. Returned same error.
Of course, I may be doing it totally wrong. I won't have time to research the webdav procedure until tomorrow, or maybe later.
That's what I used to do. I used the same Nextcloud connection information (URL, user, pass) but with the WebDAV connector. So it appears that you have confirmed that this also errors due to the OpenSSL problem.
Definitely. I connect to OwnCloud via WebDAV. There are issues with other services such as pCloud, however, which can be found in user reports here in this forum.
good and bad. good that I can connect via webdav to other cloud sites. bad, since pcloud was my first choice. but there are others.
the faq says copy everything from existing folder (nextcloud/joplin?) to new cloud joplin folder, and not to forget the .resource folder. I don't see a .resource folder.
also, the current nextcloud/joplin folder presumably is up to date with iphone joplin. but not with the windows joplin folder. can I presume that all this data with get synced to the windows joplin folder? and not deleted?
The safest way to switch nextcloud provider without risking any data loss would be:
-Make a full jex backup of your good profile
-Make a new profile on one of your Joplin clients
-Import your jex backup into the new profile, connect it to your new Nextcloud account, and let it fully sync
-Make a new profile on your other Joplin clients and sync them to your new Nextcloud account
-Once you are happy everything if working, you can delete the old profile on all clients and close your old Nextcloud account
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.
I don't know how to explain this. When in the other location my iphone didn't give error but laptop did. both connected to same network.
Check that your devices have consistent computer clocks, ideally set from a time server. A lot of sync issues can occur from clocks being a few minutes off from each other.
Maybe, however this sync issue continued from thur night till following thur morn. Only time change on either device was manually changing time zone. When the laptop returned home it was magically fixed.
Since sync now worked fine from home, I tried syncing again from a friend's wifi: failed. same, I think, error message: "write EPROTO 615680:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:....\third_party\boringssl\src\ssl\tls_record.cc:130:"
web search on error message hasn't shown me any possible solutions that can be effected from my device (eg: change how the Joplin sync code operates, or the cloud server operates). And trying to test possible fixes means finding another wifi network to test on. Then another one. Not a practical situation.
Since Joplin syncing through a nextcloud/webdav is not reliable. Looks like this is end of road with Joplin.