bitwarden / mobile

Retired Bitwarden mobile app for iOS and Android (MAUI/Xamarin).
https://bitwarden.com
GNU General Public License v3.0
153 stars 24 forks source link

App times out trying to login or synchronize the vault #3322

Closed Jb1fspq5lkuXf4LPBhz53N3bIKEESE5pAaYs8n0 closed 5 months ago

Jb1fspq5lkuXf4LPBhz53N3bIKEESE5pAaYs8n0 commented 5 months ago

Steps To Reproduce

  1. Login to a self-hosted vault that has a Let's Encrypt certificate with the new short chain

Expected Result

Connection to the vault works

Actual Result

Connection times out with error message exception message: net_http_request_timedout, 100

Screenshots or Videos

No response

Additional Context

I am self-hosting a vault behind Traefik as the reverse proxy with automatic certificate management using Let's Encrypt. I am currently trying to troubleshoot an issue with the Android App, which apparently cannot connect to the vault, even though the Web interface in the browser is perfectly working fine on the same device.

I came across this thread, which mentioned that the app requires a full-chain certificate. However since Feb 8th, 2024, Let's Encrypt now issues certificates with a shortened chain. The short chain will become mandatory for all new certificates on June 6th.

I configured Traefik to create a new certificate with the long chain and the app works fine for now. Interestingly enough the app also works with the short chain if I connect to the vault through a WireGuard VPN. I am not sure why that is.

See my comment below:

Seems like I was wrong. I just tried it again and it's not working anymore. The issue could be unrelated to Let's Encrypt. I will update the issue.

Here are some things I noticed:

  • sometimes the app actually manages to login and while the app is open I can press the synchronize button as often as I want without problems
  • closing and restarting the app then causes the app to fail again to log into the vault
  • when connected to a VPN, the problem does not appear

It could be a configuration issue on my side, however that would not explain why accessing the Vault using the browser or the desktop clients work perfectly fine and why the app actually does work sometimes. I tried to find some clues using logcat but I didn't see any related error messages there.

Operating System

Android

Operating System Version

14 / GrapheneOS

Device

Google Pixel 6 Pro

Build Version

2024.4.0 (10172)

Jb1fspq5lkuXf4LPBhz53N3bIKEESE5pAaYs8n0 commented 5 months ago

Seems like I was wrong. I just tried it again and it's not working anymore. The issue could be unrelated to Let's Encrypt. I will update the issue.

Here are some things I noticed:

Jb1fspq5lkuXf4LPBhz53N3bIKEESE5pAaYs8n0 commented 5 months ago

I think it's still an issue with the TLS certificates. Previously I used Cloudflare (which serve their own certificates) to route the traffic to my instance and the app worked without any problems the whole time. For testing I turned that back on and the app works fine again.

I am using the default ACME configuration with Traefik v3.0.1, so I'm not sure if it is something I can fix on my side here.

EvaivL8ItjVaM9KlFGdq2Mjd79XVoptK2litEfF commented 5 months ago

Hi @Kaskadee ,

I think your error could have its origin in a misconfiguration of network settings or DNS or firewall in your self-hosted instance.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our contact form, so we can continue troubleshooting: https://bitwarden.com/contact/

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation (https://bitwarden.com/help/) or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!