search

nextcloud / passman-android

:key: Android app for Passman.
https://passman.cc
GNU General Public License v3.0
93 stars 30 forks source link

Trust anchor for certification path not found when trying to connect via https #46

Open adocampo opened 6 years ago

adocampo commented 6 years ago

Hi there,

After reinstalling the custom ROM on my mobile device (same ROM, new version) passman alpha stopped working properly. If I recall correctly, it did work just fine before. The fact is, I can't connect to my NC via HTTPS, HTTP connects just fine. I have a dockerized NC with and one apache reverse proxy with the Let's Encrypt certs. Usual nextcloud clients and web is working as expected, even other apps like notes, calendars, contacts, etc... just passman fails to connect.

The error it gives is: Network error: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Don't know how to debug more to give you something to see. By the way, you can see my let's encrypt certificate on https://cloud.docampo.net Best, Angel

brantje commented 6 years ago

Afaik, this happens because Android is missing the root cert of LE. Can you try importing the cert into your phone and try again?

adocampo commented 6 years ago

Nop, even downloading the cert and installing it on android works. Now the error doesn't pops up, but... nothing. The app doesn't start either.

PS: I can create an account for you to test if you want to dig in...

mich04 commented 6 years ago

updatedscreenshoot I think I might be having the same issue. I have a self signed certificate. I can access my server through any web browser okay after adding the exception as well as the Nextcloud app and desktop client. I exported the crt from one of my Linux machines and installed it. I can see it in my user certificates on the device. I am running Android 8.1.0 and Passman 0.14-NIGHTLY.

mich04 commented 6 years ago

I got a new certificate from Let's Encrypt which resolved this for me. It would seem that self sign certs are just trouble.

nightduck commented 6 years ago

I was able to correct this error by installing an intermediate certificate on my apache server. See this page for instructions on how to do that.

IBBoard commented 5 years ago

This looks like a duplicate of #25, which I'm still having problems with ☹