I get this error, but I’m sure that the URL is correct! (it follows the same format of Joplin’s example, too)
my WebDAV link is https://cloud.xplosionmind.tk/remote.php/dav/files/xplosionmind/.
MacOS app, version 1.0.179
What should I do? Is it a bug or it’s just my problem?
Thanks a lot!
Try using webdav not dav I did not notice that last time…
Edit: That’s odd my NC18 box now shows the dav url with dav but my Joplin client has always used webdav which I am sure is what it was on a previous NC version when I set Joplin up…
If I try to sync Joplin using a webdav URL with dav I get the same error as you.
If I test the sync in Joplin using the webdav URL with webdav, a URL that has been working for ages, I get another error where it looks like Joplin is pulling down the NC login page. However if I ignore it Joplin does sync.
I have no idea what is at fault here Joplin, Nextcloud or both!
It popped up in my mind that maybe installing Joplin WEB API for Nextcloud could help, but even if I can’t: the latest supported version of Nextcloud is 17, I have Nextcloud 18. Btw probably it has nothing to do with this problem anyway.
Although an error was given sync did work afterwards.
I think I have found a way to sync to Nextcloud 18 without errors. Nextcloud's webdav urls have changed since I first synced Joplin (and, it seems, since the Joplin FAQ was written)
Do NOT use the Nextcloud sync option use WEBDAV
For the webdav URL use the one EXACTLY as provided by the Nextcloud File app's "Settings". DO NOT add the "Joplin" folder path. It will look like https://<url>/remote.php/dav/files/<username>/ Where <url> and <username> refer to your Nextcloud server URL and the user account you are using.
Enter the unaltered webdav url and your NC username and password and press "Check synchronisation configuration". You should get confirmation all is well
ADD the Joplin folder path to the end of the webdav url so it now looks like https://<url>/remote.php/dav/files/<username>/Joplin/ (or whatever the name is of the folder you are using for your Joplin notes)
Press "Check synchronisation configuration" again. You should get confirmation all is well
Press "OK" or "Apply" to confirm the settings
Sync the client
If you add the Joplin folder name before your first sync configuration check you will get an error.
I did not find this due to any "leet" coding or webdav "skilz". I just kept trying different permutations until it worked...
So did I. Had set it up ages ago. Today, with "Nextcloud" sync working, I went to the sync settings page. I saw that the last sync test result was unknown. I pressed the test and got an error that webdav was not configured properly even though sync worked and continued to work. The last test result now showed as error.
After much faffing about I found that the easiest way to get an error free setup was to use the instructions for webdav as per the Joplin FAQ (using the /webdav/ URL without the account name) but using the Webdav connector and not Nextcloud.
My solution to continue using the nextcloud adapter was to backup my local copy of my notes to a jex. Then remove the /Joplin sub directory from my dav address. Proceed to sync it then was able to connect to my nextcloud instance again. After that I re-added the /Joplin sub directory to the dav address and re-synced. Once it started to populate the /joplin folder i just imported my backup and deleted the conflicts.
I am using linux on the desktop and android with my own nextcloud server with every variation of the url and none with work. Now that tomboy and ownnote have been abandoned I thought I would try this. https://myserverurl/nextcloud/remote.php/webdav/files/$USERNAME/joplin Any help?
It was nice to have something that works with any iteration of Joplin, in this case, the appimage that runs on the linux desktop. Sadly, I tried it with the Joplin app for the android and it wouldn't work.