Android app not connecting to self hosted instance

[PaulMcF1987]

I have had a problem for quite a while where I was under able to add new logins via the Android app. I was getting the below error

An Error occurred Exception Message: connection Failure

(I tried taking a screenshot but the app wouldn't allow it)

Today, I decided to clear the app data and start from scratch.

I set up my self hosted address which I have checked multiple times and it is correct.

I entered my username and then when asked for the password, I get the same error as mentioned above.

I use the chrome/Firefox extentions and they sign in fine, it is only on the Android app that i have the issue

I have found this
bitwarden/mobile#3360

Seems to be a big issue.
Although apparently related to older versions of Android
I am using a galaxy s22 with android 14 which I wouldn't say is an old version

[kpfleming]

Log in to the web vault, go to the admin page at /admin, and grab the diagnostics report to paste it here.

[BlackDex]

Also, try Chrome to connect to the web-vault.
If you use a self-signed cert, that might cause issues.

Also, sometimes DNS has issues if you use DoH (Secure DNS) system wide.

[PaulMcF1987]

@kpfleming
Is this what you need

Server Installed **Ok** 1.32.7
Server Latest 1.32.7
Web Installed 2024.6.2c
Database SQLite: 3.46.0
Checks
OS/Arch linux / x86_64
Running within a container Yes (Base: Debian)
Environment settings overridden No
Uses a reverse proxy Yes
IP header **Match** Config/Server: X-Real-IP
Internet access **Ok** Yes
Internet access via a proxy No
Websocket enabled **Error** Yes
DNS (github.com) **Ok** 140.82.121.3
`Date & Time (Local) Server: 2025-01-12 16:01:15 +00:00

Date & Time (UTC) Server/Browser Ok Server NTP Ok Browser NTP Ok
NTP: 2025-01-12 16:01:17 UTC
Server: 2025-01-12 16:01:15 UTC
Browser: 2025-01-12 16:01:15 UTC

The only issue there is an error at Websocket Enabled

@BlackDex Im not sure what you mean by using chrome to connect? Chrome on my android device? I get in fine
I can use the extension fine on chrome/firefox

[BlackDex]

I mean the chrome browser, if you can access the web-vault or not. That sometimes help indicate if the phone is able to connect to the server or not.
But if that is the case, i see no reason for the Android app to being able to connect.
I would suggest to check the logs of both your reverse proxy and Vaultwarden during the time you try to login and see what you are getting there. If you see nothing, something goes wrong on the client side.

You could try to check with adb logcat and see if you get anything useful there.

[PaulMcF1987]

@BlackDex the webvault works fine on chrome, no issues at all

From the Vaultwarden logs

[2025-01-12 16:27:05.502][request][INFO] GET /notifications/hub?access_token=xxxxxxx
[2025-01-12 16:27:05.503][response][INFO] (web_files) GET /<p..> [10] => 404 Not Found

I cant see any issues in the nginx logs

[BlackDex]

Those are not logs from the Android client, as they do not use websocket connections.
So, it looks like there is no connection made at all from the Android client.
The only thing i can think of is wrong configuration of the self-hosted domain in the Android client.

Make sure you only fill in the first input, and leave the others empty, and also make sure you provide https:// and port numbers if those are needed too.

[PaulMcF1987]

@BlackDex
The configuration is correct. It is the same configuration that I use on the browser extensions.
I have put my domian in the top box and the rest are empty

It was working fine for a long time, then all of a sudden stopped syncing. with me error message mentioned in my question. I cleared the app data and now cannot connect at all, with the same error message.

It seems to be a common problem with people using bitwardens own server - bitwarden/mobile#3360

I have found the following logs but not sure if they are related. they seemed to populate around the same time as I tried logging in

2025-01-12 17:50:23 | info | sshd [2840481]Security/authorization messages [4] | Unable to negotiate with 218.92.0.215 port 49275: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth] -- | -- | -- | -- 2025-01-12 17:50:18 | err | sshd [2840415]Security/authorization messages [4] | error: kex_exchange_identification: Connection closed by remote host

[BlackDex]

Those do not seem to be related to Vaultwarden or the Bitwarden client at all.
The repo you link to is not the repo for the new Android Client, that should be bitwarden/android not bitwarden/mobile.

You could try the testing tagged version maybe, but i doubt that will help, as you do not see anything in the reverse proxy logs or Vaultwarden logs, that to me indicates the clients doesn't connect, and not a server side issues.

Other then shifting through your adb logcat logs when trying this, I have no other options I can think of.

[PaulMcF1987]

@BlackDex is there a particular tag I should filter in logcat?

I have downloaded an app to view logs from the phone. It doesnt seem overly good though

[PaulMcF1987]

I dont have a bitwarden hosted set up.
I can assure you that the domain is 100% correct.
I use the same set up on the browser extensions

Have you heard of keyguard for bitwarden?
I'm thinking, if that is reputable, i will try and connect and see how it goes

[BlackDex]

You can always try it. I didn't used it my self.

[PaulMcF1987]

Tried on keyguard

Ther error was
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

[BlackDex]

Looks like your certificate is not ok. It's either missing chain certs, or it's not a valid cert or self-signed.

[PaulMcF1987]

I have reissued the SSL Cert and that seems to have sorted the problem. Thank you for your help