Upgrade StorageZotero Android: WebDav Trust anchor for certifacte path not found
Hey, I am using the Zotero Android App with file syncing via WebDAV with the domain
https://webdisk.ads.mwn.de/hcwebdav
This was working flawlessy on the desktop app and the android app until yesterday, when the android app started giving me the error
"HTTPS error: Trust anchor certificate path not found" when trying to verify the webdav server.
I did go ahead and checked whether the certifcate of that domain are working via https://www.ssllabs.com/ssltest/ , and also verified via my browser (on my phone) that the certificate is valid.
I also reinstalled the Zotero App without any success.
Debug ID D580269613
Thanks so much for your help and the wonderful Zotero program(s)!
https://webdisk.ads.mwn.de/hcwebdav
This was working flawlessy on the desktop app and the android app until yesterday, when the android app started giving me the error
"HTTPS error: Trust anchor certificate path not found" when trying to verify the webdav server.
I did go ahead and checked whether the certifcate of that domain are working via https://www.ssllabs.com/ssltest/ , and also verified via my browser (on my phone) that the certificate is valid.
I also reinstalled the Zotero App without any success.
Debug ID D580269613
Thanks so much for your help and the wonderful Zotero program(s)!
-
benjaminbogAlso I tried the domain on another Android device in the Zotero app, and there it is working.
-
dstillmanIt's a new certificate as of a couple weeks ago, and the root certificate (which may or may not have been the previous one) is not in the Java trust store. It supposedly is and has been in the Android trust store, but it's possible there's some issue there — there are a few oddities about the server's certificate setup. (It's also possible you added an exception in your browser.) If you can update Android, you should do so.
-
benjaminbogYes I noticed the certificate issue with Java as well. For now I was able to download and install these certificates manually, which fixed the issue. Though I have no idea how this could have happened from one day to the next without any apparent changes.