joplin
joplin copied to clipboard
laurent22
Synchronization with TrueNAS WebDAV fails, but checking synchronization configuration succeeds.
Environment
Joplin version:
Joplin 2.8.8 (prod, linux)
Client ID: aeb346e51ec146deb037b443514681bd
Sync Version: 3
Profile Version: 41
Keychain Supported: No
Revision: c2a6a13
Platform: Linux and iOS OS specifics: Ubuntu 21.04 and iOS
Dear all,
first of all thank you for this great software!
I am trying to configure a WebDav instance running on TrueNAS for Joplin. Current settings are like so:
The synchronization configuration in Joplin returns success with the TrueNAS WebDAV settings above and the following settings in Joplin:
But actual synchronization in Joplin fails with this error:
Completed: 27/07/2022 23:03 (251ms)
Last error: Error: MKCOL locks/: Unknown error 2 (403): <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access this resource.</p> </body></html>
And as screenshot:
I tested this both with Ubuntu and iPad Joplin clients and both exhibit the same behavior, which suggests that it has to do with my WebDAV configuration. However, WebDAV is working with Zotero with the same configuration (but obviously a different URL/path).
I would be grateful for your support. Best regards and thanks, Michael
PS: As a related question: I had to change the authentication from "Digest Authentication" to "Basic Authentication" in the TrueNAS settings above or else I would get the following error while testing the sync settings (note that for synchronizing Zotero it works correctly with both):
Error. Please check that URL, username, password, etc. are correct and that the sync target is accessible. The reported error was:
PROPFIND : Unknown error 2 (401): <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Unauthorized</title> </head><body> <h1>Unauthorized</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html> (Code 401)
Is this expected behavior?
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.