When I'm in offline/airplane mode I get failed to connect

Ask the Community Password Manager
, ,
1

hello if I use vaultwarden as a server, if I lose connectivity and launch bitwarden, I get an error, I can ignore error, and use bitwarden offline on my android device.

I turned on flight recorder logs and see (when trying to connect to my vaultwarden server)

My understanding is bitwarden supports offline/no connectivity scenarios. So why am I getting this error, can bitwarden just silently fail in these scenarios where there is a custom server involved?

2026-02-25 13:32:45:019 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-02-25 13:32:45:042 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2026-02-25 13:32:47:263 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.SettingsRoute$Standard/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2026-02-25 13:32:50:230 – DEBUG – f – Network status change: Wifi(strength=GOOD)
2026-02-25 13:32:50:239 – DEBUG – h – Current environment: SELF_HOSTED
2026-02-25 13:32:50:241 – DEBUG – h – Current environment: SELF_HOSTED
2026-02-25 13:32:50:241 – DEBUG – h – Current environment: SELF_HOSTED
2026-02-25 13:32:50:303 – DEBUG – c – App is foregrounded
2026-02-25 13:32:50:326 – DEBUG – a – MainActivity destination changed: com.x8bit.bitwarden.ui.platform.feature.rootnav.RootNavigationRoute
2026-02-25 13:32:50:345 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute
2026-02-25 13:32:50:360 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.auth.feature.vaultunlock.VaultUnlockRoute$Standard/{encodedData}
2026-02-25 13:32:50:742 – DEBUG – BitwardenNetworkClient – → GET
2026-02-25 13:32:51:097 – DEBUG – BitwardenNetworkClient – ← HTTP FAILED: java.net.ConnectException: Failed to connect to omitted/127.0.0.1:443. /api/config (354ms)
2026-02-25 13:32:51:097 – WARNING – NetworkResultCall – Network Error: https://api.bitwarden.com/config
java.net.ConnectException: Failed to connect to omitted/127.0.0.1:443
at fw.c.i(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:136)
at fw.c.d(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:28)
at fw.j.a(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:3)
at ab.c.run(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:407)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
at java.lang.Thread.run(Thread.java:1119)
Caused by: java.net.ConnectException: failed to connect to omitted/127.0.0.1 (port 443) from /127.0.0.1 (port 54436) after 10000ms: isConnected failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.isConnected(IoBridge.java:347)
at libcore.io.IoBridge.connectErrno(IoBridge.java:237)
at libcore.io.IoBridge.connect(IoBridge.java:179)
at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
at java.net.Socket.connect(Socket.java:646)
at fw.c.i(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:79)
… 6 more
Caused by: android.system.ErrnoException: isConnected failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.isConnected(IoBridge.java:334)
… 15 more
– java.net.ConnectException: Failed to connect to omitted/127.0.0.1:443
at fw.c.i(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:136)
at fw.c.d(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:28)
at fw.j.a(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:3)
at ab.c.run(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:407)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
at java.lang.Thread.run(Thread.java:1119)
Caused by: java.net.ConnectException: failed to connect to omitted/127.0.0.1 (port 443) from /127.0.0.1 (port 54436) after 10000ms: isConnected failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.isConnected(IoBridge.java:347)
at libcore.io.IoBridge.connectErrno(IoBridge.java:237)
at libcore.io.IoBridge.connect(IoBridge.java:179)
at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
at java.net.Socket.connect(Socket.java:646)
at fw.c.i(r8-map-id-34e916b99be6637dd6e0b022a3a2af0b5dee3951071794ba637fe24b41f05950:79)
… 6 more
Caused by: android.system.ErrnoException: isConnected failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.isConnected(IoBridge.java:334)
… 15 more

Option to Turn off autologout if server returns an error
3

@shayaantx Welcome to the Bitwarden Community Forum!

It seems, you are using an unofficial server software, which is not supported by Bitwarden, as it is an independent product. From time to time, there will be compatibility issues between the official Bitwarden client apps (browser extension, mobile app, desktop app…) and an unofficial server product, when Bitwarden implements changes to its own server software and/or client apps. “…Bitwarden cannot guarantee that official clients will work perfectly with non-official servers.”

(Also due to this - and for other reasons - we recommend using the official Bitwarden server software.)

It is generally not possible for members of the Bitwarden community (users or developers) to help with such issues - and with issues of the unofficial server itself. Please seek support in their community spaces.

If you can replicate your issue on an official Bitwarden server, feel free to open a new thread here.