Operating system
Linux
Joplin version
3.5.13
Desktop version info
Joplin 3.5.13 (prod, linux)
Appareil : linux, Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
ID client : a5f7490955f442e6b6fe8eac3b7b4f36
Version de Synchro : 3
Version du profil : 49
Trousseau supporté : Non
ID d'instance alternatif : -
Backup: 1.5.1
Freehand Drawing: 4.2.0
Sync target
WebDAV
What issue do you have?
Since 2 or 3 months I have a "PUT" error while synchronising.
I have written to Infomaniak and here is their reply :
Citation
Thank you for contacting Infomaniak Support.
We do not provide support for the WebDAV protocol or for third-party tools such as Joplin.
From what we can see, you are using the correct kDrive ID, an app password, and a WebDAV-compatible plan. Everything looks good on our end.
We recommend that you check your network, try using a different connection, or contact Joplin support directly.
End of citation
Please see screenshots for either Desktop under Linux or Smartphone under Android
Screenshots
I think that means their WebDAV protocol is not guaranteed to work correctly and they're not going to help you. You should look for another provider
@mrjo118
I wasn’t expecting that sort of response; it’s a bit of a cop-out to pass the buck without any explanation.
It would be more constructive to tell me what the error reported by Joplin means and what solutions might be worth considering.
Perhaps there’s someone more cooperative on this forum, as I’ve come across in the past.
Sorry for not giving further explaination.
WebDAV is a web protocol for managing files on a server. Some Cloud providers claim WebDAV support but don’t fully follow the protocol. It's not uncommon for the (rare) hosted Cloud storage providers that offer WebDAV, to offer WebDAV connectivity to their service, but say they do not offer support for it. What they usually mean is the access is available, but they don't actively maintain the code / server for providing it, other than security upgrades.
Due to deviations from the standard protocol, it is not possible for Joplin to support every single WebDAV provider. The reason I'm suggesting you should look for another provider, is it's unlikely you're going to get it to work with Joplin if the server is hosted (rather than self hosted, which you could configure yourself) and the provider is unwilling to support you with it. The only way to fix the error you are getting, would be to make changes on the server side, regardless of whether it is a compatability issue vs a configuration issue.
Thank you for your answer.
However I would know :
This could help in solving the problem, and eventually ask to the service provider.
Ok, I did not realise you meant that you had it working previously, but now it no longer works.
Did the error start happening after an upgrade of the Joplin app, or just stopped working out of the blue? Without getting too technical, the error indicates the server received something unexpected from the client (Joplin).
If the error starting is not tied to a Joplin app upgrade, then as nothing could have changed on the Joplin side, it would indicate Infomaniak has changed something at their end.
It seems really that it happened after an upgrade first on Joplin App on Android, then on my linux desktops. But I cannot assure that because I procrastinated too much to be sure...
On their side Infomaniak have checked my access configuration and they found it was OK.
But if I check my configuration by the way of Joplin App, it seems also OK.
Then, what is the "unexpected event" the error message indicates ?
What was the previous Joplin version before you upgraded?
Did you happen to upgrade from Joplin 3.4?
I had a look at the changelog and there is a change in Joplin 3.5.1 which possibly could be causing the error All: Fixes #12249: Change default content-type for Webdav connector to application/octet-stream by pedr · Pull Request #13053 · laurent22/joplin · GitHub
I asked ChatGPT about the possible causes of the error and one of the possible causes relates to what that PR changed:
Incorrect request headers
Missing or wrong Content-Type, Content-Length, or auth headers can cause the server to reject the request in a way that surfaces as 409.
Really I don't know.
Till now it worked well and I did not care what version it was.
Sorry.
It is possible that happened because I use Joplin for many years !
If it is the cause, what is the possible correction to do on my config ?
Do you have a spare device which you can install an older version of Joplin, to check if the sync works on that version? As using WebDAV on kdrive requires a paid account, I cannot test this myself.
Would you be able to test this using the following version of Joplin? Release v3.4.12 · laurent22/joplin · GitHub
The reason I suggest to use a spare device is because you cannot downgrade from Joplin 3.5 to 3.4 unless you delete the local data. But if you don't have a spare device, you could uninstall Joplin, delete the folder at ~/.config/joplin-desktop and then install the older version. Then you will have a blank profile and will need to sync to redownload all the data
@MarcDriver Ok, ignore my last post about trying an older version. I found that kDrive offers a 30 day trial of kDrive solo, so I have set up account for testing.
I am able to sync Joplin data to kDrive in both v3.4.12 and v3.5.13 of Joplin desktop without any issues. Therefore there aren't any Joplin client side changes which is causing this issue. This means either something has changed on your specific kDrive account, or the Joplin data on your account has somehow got corrupted. As Infomaniac will not offer you support with this, the only thing I can suggest is to follow this process How to fix synchronisation issues and start over, which will replace the server data with a known good copy of your local data
Without seeing this last post I would have replied that it exists a free version of KDrive; I have one free and one with subscription, this last I use for my Joplin sync.
I will test your proposal.
But before I have connected a PC on which I have a version of Windows 11 and on which I have an old Joplin version connected on a Dropbox cloud I have still and that I don't use since 2024.
I have tried to sync and I had an error message a little bit different from the one I have with Infomaniak (see attached).
In the mean time I'll try to fix the sync.
(attachments)
JOPLIN_2026-05-08_Joplin 3.2.12 (prod, win32).txt (221 Bytes)
