Webdav sync is broken on iOS17.5

Operating system


Joplin version


Sync target


What issue do you have?

Dear Support Team,

I hope this message finds you well. I would like to bring to your attention an issue that I have encountered while using the application.

Upon reviewing previous tickets in this community, I noticed similarities to my current concern, although there are distinct differences this time around.

Following the recent upgrade to iOS 17.5, I observed that data synchronization between the local device and the remote WebDAV server has not been occurring, despite the absence of any error messages during the synchronization process.

In an effort to troubleshoot, I meticulously verified the synchronization settings and encountered an error message prompt suggesting to "Please check that the URL, username, password, etc. are correct..." after clicking on "check synchronization configuration".

For reference, I am using HTTP + IP address instead of domain name for the WebDAV URL configuration(see screen shot).

It is worth noting that the desktop version of Joplin seamlessly interacts with the aforementioned WebDAV server.

Thank you for your attention to this matter.

Warm regards


Log file

mobile-log-0605b (1).txt (9.24 KB)

Joplin 12.14.8 on iOS 17.5.1 is synchronising seamlessly here with Joplin 2.14.22 on MacOS 14.5 via my WebDAV server for which I too use static IP addressing. Only the port is different. Thus, Webdav sync is not, in universal terms, "broken". I have seen the other posts to which you refer, so wonder what might be in common between them?

I also cannot sync my iOS 17.5.1version iPhone to a WebDAV server in my LAN by IP number. It shows this error on"Check synchronisation configuration": "Network request failed."

I can sync with my Mac OS14.5 fine. There is one sync setting in Joplin on the Mac that I do not find in the sync setting on the iPhone: "Ignore TLS certificate errors." I believe that may be why it will not sync.

1 Like

Hi Patricr, I totally agree with you. TLS certificate might be the root cause.
One more thing, It does work well on my old iPhone(iOS12) with the same settings.