iOS cannot access Self-hosted

Help
1

I see that there has been an issue with people making use of the Bitwarden iOS Client when upgrading to vaultwarden (say from bitwarden). I am running vaultwarden from ContainerManager via my Synology NAS.

I am having troubles accessing vaultwarden from my iOS device. I think it’s due to a timeout with connection.

Server info:
Self-hosted with SSL from LetsEncrypt

Server Installed Ok - 1.32.6
Server Latest - 1.32.6
Web Installed - 2024.6.2c
Database - SQLite: 3.46.0

I can access the server from my desktop using the URL(domain) but also from the Bitwarden browser extensions.

I cannot access it at all on my iPhone.
I’ve have WiFi on and and WiFi off and cannot access the URL or via the Bitwarden iOS app.
I do not have Privacy Relay enabled either.

I do have an internal DNS server running for split DNS but that I don’t think is an issue as when I drop into a terminal the URL I use resolves to the proper IP still (external) - Disabling WiFi of course takes the split DNS out of the question.

Anyone else have issues trying to connect after upgrading to the lastest Vaultwarden?

2

I’m going to try and update as best as I can as I have finally got it working.

Server Installed: 1.34.1
Server Latest: 1.34.1
Web Installed: 2025.5.0
Database: SQLite: 3.49.1
iPhone: 12 Pro - iOS 18

I re-did my Let’s Encrypt Certificate for my Synology device (it’s set to default too). I then checked with SSLLabs that it’s valid and correct and had no issues.

I ensured my firewall’s (ISP modem/router) port forwarding was correct as I am also using Reverse Proxy (443 to 5151)

I started by ensuring I could get to the web UI (on my iPhone) via DDNS and not the BitWarden app. The re-creating the cert seemed to have fixed that issue.

Next was to tackle the local access with the DDNS. Since my router doesn’t support Hairpin Nat, I do have DNS Server running. I had to create a new Primary zone and a new A Record to point the subdomain I was trying to access.

After that was all done and I could visit the web UI both on Cellular Network and WiFi Network, I loaded up the BitWarden client, picked-self hosted, ensured the DDNS value was set the same and I could finally log in!