Operating system
macOS
Joplin version
3.4.6
Desktop version info
Joplin 3.4.6 (prod, darwin)
Device: darwin, Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Client ID: b20a381c1b7947b7a9ab7ddce9b93214
Sync Version: 3
Profile Version: 48
Keychain Supported: Yes
Alternative instance ID: -
Revision: 4128061
Sync target
WebDAV
What issue do you have?
Just installed 3.4.6 and getting error "Last error: TypeError: Failed to fetch". I closed and reopened with same issue
Screenshots
I have the same issue on Windows 11 and Linux (OpenSuse Tumbleweed). Both are up to date. The synchronization via WebDAV no longer works.
Do you use self-signed certificates?
These issues on GitHub may be linked to what you are seeing.
#13009
#13010
I don’t actually use self-signed certificates, but the host name in the certificate used does not correspond to the (internal) host name used by the internal Webdav address. But I have always been able to circumvent that problem by clicking “Ignore TLS certificate errors” in the Synchronization setup.
Using the same “Ignore TLS certificate errors”
Definitely a problem with TLS and presumably self-signed certificates or those with an invalid host name. HTTP works fine.
mattt
21 August 2025 14:46
8
Same Problem here, webdav via https selfsigned cert bc. hosting in my homelab, ignore tls errors is enabled.
Same here. Worked until updating to Joplin Desktop v3.4.6. I also use a self-signed certificate and webdav (via Nextcloud).
I just found another thread which says release v3.4.7 will fix it: Problems with webdav
Confirmed that version 3.4.10 fixed the issue. Sync is happy again!
1 Like
system
Closed
2 October 2025 02:33
11
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.