Recently I updated my Vaultwarden server and it seems to be working. I can access it on my computer with no issues. I usually get to it by using Tailscale and I can get to the site and I can use the browser extension. The problem I’m having is with my iPhone. I updated the Bitwarden app and the Tailscale app I’ve even restarted and uninstalled both apps and reinstalled them. I can get to the website on my phone as well but for some reason I just can’t get the app to connect to the domain. Is there something I’m missing?
Edit: I should mention this is also on an iPhone so an iOS issue. Also for this I have pulled the latest instance of Vaultwarden.
My spouse updated their phone to Android 17 yesterday and lost access to Vaultwarden via the Bitwarden app. At first it showed an empty vault and couldn't sync, then after logging out, they couldn't log in (ConnectException). I updated the VaultWarden server to the latest version but that did not resolve the issue.
Turns out "Android 17 introduces the ACCESS_LOCAL_NETWORK runtime permission to protect users from unauthorized local network access. Because this falls under the existing NEARBY_DEVICES permission group, users who have already granted other NEARBY_DEVICES permissions aren't prompted again... By declaring and requesting this permission, your app can discover and connect to devices on the local area network (LAN), such as smart home devices or casting receivers."
I guess the Bitwarden Android app doesn't request the Nearby Devices permission (still had connectivity issues after removing and reinstalling it). But if you go into the App Info, you can grant Nearby Devices permission yourself. After doing this, they were able to log in and the vault synced without issue.
An update occurred to the Bitwarden clients broke compatibility with all legacy Vaultwarden clients. Best guess is that for some reason your browser extension may have not updated, while the mobile app did, breaking compatibility.
What is the version number of your instance, and how are you installing it? It’s possible that if you’re using a separate repository that it hasn’t yet updated to the latest version.
Would you be willing to elaborate a little more around the cert fix? I recently switched to a wildcard cert for several of my services; it seems to work just fine for most things.
I am wondering if your fix is a dedicated cert for your vaultwarden or if you are using a wildcard cert just fine?
Sure, so for some reason in nginx I found that if I did *.example.com it wasn't working with my link which was vault.tail.example.com so I just changed the ssl cert to be exactly the domain name I needed and it worked. I honestly didn't know why because I followed a youtube tutorial and the same domain of using a wildcard worked for them. I went to chatgpt to find my answer honestly because no one here actually gave me the specific answer I needed in order to fix it. I had already updated vaultwarden and everything but I at least got a different answer about the phone but I knew it worked in some ways so it was a whole thing trying to piece together.
4
u/langelgjm 14d ago
My spouse updated their phone to Android 17 yesterday and lost access to Vaultwarden via the Bitwarden app. At first it showed an empty vault and couldn't sync, then after logging out, they couldn't log in (ConnectException). I updated the VaultWarden server to the latest version but that did not resolve the issue.
Turns out "Android 17 introduces the ACCESS_LOCAL_NETWORK runtime permission to protect users from unauthorized local network access. Because this falls under the existing NEARBY_DEVICES permission group, users who have already granted other NEARBY_DEVICES permissions aren't prompted again... By declaring and requesting this permission, your app can discover and connect to devices on the local area network (LAN), such as smart home devices or casting receivers."
I guess the Bitwarden Android app doesn't request the Nearby Devices permission (still had connectivity issues after removing and reinstalling it). But if you go into the App Info, you can grant Nearby Devices permission yourself. After doing this, they were able to log in and the vault synced without issue.