Cryptic TypeError in WebDAV Sync

[lukedink]

So - I've been using IceDrive to sync Joplin (2.6.10) via WebDAV between my devices (relatively) successfully for a while. For now, just two Win 10 computers and an Android phone. Today, everything stopped syncing and I persistently get this error across all my devices:

Cannot use 'in' operator to search for 'd:multistatus' in null

TypeError: Cannot use 'in' operator to search for 'd:multistatus' in null
at WebDavApi.valueFromJson (C:\Program Files\Joplin\resources\app.asar\node_modules@joplin\lib\WebDavApi.js:144:72)
at WebDavApi.arrayFromJson (C:\Program Files\Joplin\resources\app.asar\node_modules@joplin\lib\WebDavApi.js:182:15)
at FileApiDriverWebDav.list (C:\Program Files\Joplin\resources\app.asar\node_modules@joplin\lib\file-api-driver-webdav.js:136:32)
at processTicksAndRejections (internal/process/task_queues.js:95:5)

I've re-checked my WebDAV settings multiple times (credentials, etc.) and tried using the latest production build of the Windows app. Does anyone know what could have happened here? Theoretically, it could be a problem with IceDrive and not a Joplin issue.

First post here, so let me know if I need to add any more information.

[graphit0]

Welcome to the forum

There've been a few issues in the past with iceDrive, so even from the get-go, I suspect the provider breaking something without warning

You may try temporarily changing the provider and see if it helps

Here are the topics, the errors are different but one way or another it was caused on the server side:

Sync with Icedrive WebDAV

Hi, I just stumbled across this post through a google search. I've opened a ticket with Icedrive support in december 2020. I've provided them with the exact error message for Joplin (i also had difficulties with Enpass). Their final answer came after a few days: Hi Laurens, We're sorry to say that as of Jan 1st we have decided to drop WebDAV support, in some reason due to the problems you are experiencing above - It is a very old protocol and many 3rd party apps just dont use it properly, …

Upgrade Issue

Got an upgrading issue on my ubuntu 20 machine. My version is Joplin 2.3.5 (prod, linux). Joplin is not telling me what version it wants to upgrade to, just that my client has to be upgraded before it can start synchronizing my webdav directory again. This is the full error: GET info.json: Unknown error 2 (429): Error: GET info.json: Unknown error 2 (429): at newError (/app/joplin-desktop/resources/app/node_modules/@joplin/lib/WebDavApi.js:414:11) at WebDavApi.exec (/app/joplin-desktop/reso…

Joplin 2.3.5 and Icedrive

Hi there, it appears that nothing changed regarding Joplin and Icedrive sync by WebDAV. It doesn't matter if one does create a folder for Joplin or not, the Error message stays the same: Unknown Error 2 (429) with the PUT command. The login seems legit though [login config correct] Changed the connections to one but the error still prevails. Now I wonder if someone found a way to sync the data to android by using the file system method instead of WebDAV. I somehow can't make head or tails …

[lukedink]

Ah, yeah I was afraid of that. It seems like every other week Joplin stops being able to sync and gives me some error. This was my second support ticket I've opened with IceDrive about WebDAV. Wish I'd known about their issues before investing heavily in their service. I'm not really able to pay into another service at this time, unfortunately. I just need something dependable.

[graphit0]

Well, Dropbox works just fine if you have the database less than 2gb (limit of the free account). OneDrive is a bit worse in my opinion but it's 5gb. If your db is more than 5gb then I'd really suggest either self-host Nextcloud or consider the cost of Joplin Cloud. The reason is that WebDav services (of basically any provider) are pretty slow and with large databases it makes sense to move away from remote WebDav at all.

Also, it is not a requirement, but I would recommend to use a separate cloud service for Joplin alone: if you use a native sync client of a provider, it may casually interfere with Joplin's sync (or even get confused and delete few crucial db files) which in turn may result in corrupt database out of nowhere.

[lukedink]

Thank you for the helpful information. I've moved back to Dropbox for the time being (which is working fine), but I'll be looking into self-hosting NextCloud myself. It's a shame some cloud providers don't offer reliable WebDAV.