You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebDAV share folder for Joplin set up on QNAP NAS.
Synchronization settings Windows=Android; path,user,password
When checking the synchronization settings, the following error is displayed in the Android app:
Access denied: Please check username and password(401)
see logs
Expected behaviour
Error-free WebDav synchronization with the Android app
xvs03
changed the title
Error with WebDAV synchronization with the Android app <> QNAP NAS TS-433
Error with WebDAV synchronization on the Android app <> QNAP NAS TS-433
Dec 27, 2023
Double-check your username and password. On my phone Android sometimes tries to capitalize the 1st letter.
If that doesn't work then maybe check if there are any details in logs on your server.
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.
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.
Operating system
Android
Joplin version
2.13.10 ; Android 11 ; QNAP QTS 5.1.4.2596
Desktop version info
Windows 10 ; Joplin 2.13.11
Current behaviour
WebDAV share folder for Joplin set up on QNAP NAS.
Synchronization settings Windows=Android; path,user,password
When checking the synchronization settings, the following error is displayed in the Android app:
Access denied: Please check username and password(401)
see logs
Expected behaviour
Error-free WebDav synchronization with the Android app
Logs
mobile-log.log
The text was updated successfully, but these errors were encountered: