Joplin on MacOS is unable to sync to existing WebDAV target

[kmanwar89]

Operating system

macOS

Joplin version

3.0.15

Desktop version info

Joplin for Desktop

Copyright © 2016-2024 Laurent Cozic
Joplin 3.0.15 (prod, darwin)

Client ID: c8977c14a4b349f1998a0bb62759d832
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: 598677b

Backup: 1.4.1

Sync target

WebDAV

Editor

Markdown Editor

What issue do you have?

I've been using Joplin for 3+ years without issues - my sync target is a WebDAV server running on my Synology NAS and accessed via a local IP address - no DNS, no cloudflare tunnels, no external access or anything like that.

I've used Joplin successfully across Windows, Mac and Linux without issues during this time. However, it appears that my MacOS machine is no longer able to access the WebDAV share. I think the trigger is a recent upgrade to MacOS Sequoia, but as I don't have a non-Sequioa machine to test against, I can't easily validate this theory...

The error that I am presented is:

Error. Please check that URL, username, password, etc. are correct and that the sync target is accessible. The reported error was:
request to https://192.168.1.11:5006/Shared/Joplin/ failed, reason: connect EHOSTUNREACH 192.168.1.11:5006 - Local (192.168.0.70:59015) (Code EHOSTUNREACH)

192.168.1.11 is my Synology NAS, with 5006 corresponding to the HTTPS port. Again, this works perfectly on Windows and Linux - it is only isolated to MacOS, for some reason.

I have triple-checked that my username and password are correct - I went as far as testing a fresh Linux install on a spare laptop and confirmed it worked 100% as expected.

I'm happy to grab any other logs as requested, but have grabbed the console output from the Joplin app as a starting point.

Joplin_sync_errors.log (24.3 KB)

Update 1
I also tried another WebDAV client (CyberDuck) and it was able to successfully connect to the NAS using the same credentials without issues

Update 2
Same behavior using the latest pre-release 3.1.16, and no difference in behavior after deleting the ~/.config/joplin-desktop folder to clear the existing cache/settings

Update 3
Borrowed my fiancee's laptop (MBP, M1, 2020), installed Joplin 3.0.15, entered my WebDAV sync credentials and had no issues. Same LAN network, difference is MacOS Sequioa vs. Sonoma.

[dpoulton]

I am not a macOS user but an Internet search suggests that there are problems with Sequoia which are believed to be due to its buggy networking. It's a long shot but after looking at the below links it seems that it may possibly be worth checking that the macOS firewall is actually allowing Joplin through to properly connect to the webdav server??

macOS Sequoia is breaking third-party security software

https://www.pcmag.com/news/macos-sequoia-causing-vpn-web-browsing-antivirus-software-problems

macOS 15 Sequoia problems: how to fix the most common issues on your Mac

[kmanwar89]

I don't have the firewall disabled - I failed to mention that above, but it is something I actually checked last night as the thought struck my mind...

I think it is indeed a Sequoia-side behavior, just not sure where/how support looks like at this point.

[personalizedrefriger]

Based on this troubleshooting article for the IntelliJ IDEA development environment: Does navigating to Settings > Privacy and Security > Local Network and enabling "Joplin" (if present) help?

[kmanwar89]

It appears Joplin is already enabled in that settings pane

I wonder if it's more Joplin related than MacOS related, simply because of the fact that another WebDAV client (CyberDuck) works fine with the exact same credentials, but Joplin fails? Of course, it's much more likely that a MacOS change (in this case, likely Sequoia) has caused the failing behavior, but when thinking about the overall system, I feel like using that other app has somewhat ruled out the OS-specific behavior...

I guess put another way --- one would expect to see the same failing WebDAV behavior regardless of application if it was handled the same way at the OS level...right?