since few days i can't sync on my webdav. Is there any fix for that problem ?
Joplin 2.9.17 (prod, win32)
ID client : 1c8a1d66ce064154a537d359b26f6117
Version de Synchro : 3
Version du profil : 41
Trousseau supporté : Oui
Révision : a84a8e7
The full error was:
Could not upgrade from version 1 to version 2: PUT info.json: Unknown error 2 (429): You have been temporarily rate limited.
Error: Could not upgrade from version 1 to version 2: PUT info.json: Unknown error 2 (429): You have been temporarily rate limited.
at newError (C:\Users\xxxxxx\AppData\Local\Programs\Joplin\resources\app.asar\node_modules@joplin\lib\WebDavApi.js:414:11)
at WebDavApi.exec (C:\Users\xxxxxx\AppData\Local\Programs\Joplin\resources\app.asar\node_modules@joplin\lib\WebDavApi.js:444:10)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async FileApiDriverWebDav.put (C:\Users\xxxxxx\AppData\Local\Programs\Joplin\resources\app.asar\node_modules@joplin\lib\file-api-driver-webdav.js:201:10)
Seems like one of the errors pCloud users run into. Their WebDAV implementation is not up to specs, nor does rate limiting make sense for valid accounts.
If they use rate limiting it would be good to know what these limits are. Also WebDAV never had rate limiting in its specs afaik.
I suspect they just put that on top of WebDAV and thought this was a good idea. Well, WebDAV clients don't really know what to do with this kind of error, so they will basically just fail.
It is a bit strange though that the error happens at the sync target upgrade step. Unless you were mashing the sync button, Joplin would've made maybe 10 requests by that stage, I think.
But a rate limit can also be that only X requests are allowed within y hours and then no more requests are allowed ... or only 1 request every x seconds ...