![]() ![]() This should allow you to connect to the server again, using the latest version of the application, with any updates from Android. Then, open each of them and install the certificate using the 'Certificate Installer': * ()ĭownload ALL of the CA files onto the phone or other Android device you're trying to use the bitwarden app from * Download the entire trust chain (for me, certificates signed by Let's Encrypt) that was as follows: My Bitwarden_rs is running under docker with the following:ĭocker run -p 8005:80 -e ROCKET_TLS='' \ -e ADMIN_TOKEN=blablabla \ -v bitwarden:/config \ -v /ssl/:/ssl/ \ -p 443:80 \ -name bitwarden \ -restart always \ bitwardenrs/server:raspberry I tried to use some tools mentionned in this post to check for the certification, both are reporting that certificates can't be found, or certificates not present, etc. I followed this and the child page to generate my certificates and keys, so how would I check if my certificates are valid? I also have the same issue, my Bitwarden_RS self-hosted on RPI is working just fine by accessing it through a browser (even on the mobile), but the Android application reports an error (Trust anchor for certification path not found). You can get the APK from here:Īfter the login you can update to a newer version using the Play Store. I'm using a OnePlus 6 with Android 10 (OxygenOS).ĮDIT: Using the older 2.2.2 version fixes the login issue. Regardless of that I tried it with 443, and it didn't work either. I'm using the port 7070 because 443 is already being used by a other application. I already tried to debug the app using logcat, but wasn't able to find any helpful information. The server itself is only reachable in my LAN. ![]() The certificate chain is set correctly (I've tested it with several tools, there's no problem). I'm using a LetsEncrypt wildcard certificate. In the app itself I try to connect to the server with: There is a problem connecting to the server Matched: POST /api/accounts/prelogin (prelogin) POST /api/accounts/prelogin application/json charset=utf-8: ![]()
0 Comments
Leave a Reply. |