Bitwarden App: "An error has ocurred" on Samsung Galaxy S23 FE

[vfgKielIT]

I am using vaultwarden server on docker together with bitwarden app in our company for quite a while.
As webserver we use apache2 as reverse proxy.

Two weeks ago I suddenly got "An error has ocurred" on my smartphone. I cannot login any more via bitwarden app. Everything else is still working fine.

I thought that probably there is a version-conflict between vaultwarden-server and the bitwarden app. So I updated to vaultwarden-server 1.34.3 and installed the bitwarden app new (after emptying cache and data).

But the error persists.

This is the error-message in total:

Stacktrace:
retrofit2.HttpException: HTTP 404
com.bitwarden.network.core.NetworkResultCall.toNetworkResult(r8-map-id-bf57a793dd4aae29ab5e880b2a965c871cb21b98120207e5a21b66d366f5e0bf:9)
com.bitwarden.network.core.NetworkResultCall.access$toNetworkResult(r8-map-id-bf57a793dd4aae29ab5e880b2a965c871cb21b98120207e5a21b66d366f5e0bf:1)
com.bitwarden.network.core.NetworkResultCall$enqueue$1.onResponse(r8-map-id-bf57a793dd4aae29ab5e880b2a965c871cb21b98120207e5a21b66d366f5e0bf:15)
fe.q.G(r8-map-id-bf57a793dd4aae29ab5e880b2a965c871cb21b98120207e5a21b66d366f5e0bf:13)
uv.m.run(r8-map-id-bf57a793dd4aae29ab5e880b2a965c871cb21b98120207e5a21b66d366f5e0bf:57)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
java.lang.Thread.run(Thread.java:1119)

Version: 2025.11.0 (20967)
Device: 📱 samsung SM-S711B 🤖 16@36 📦 prod
CI: 🧱 commit: bitwarden/android/release/2025.10-rc38@6d71f0c5d66a466a20e4636be438609d2703063c
💻 build source: bitwarden/android/actions/runs/19309927902/attempts/1

Is this a know problem? What can I do?

I read this message from yesterday: #6524
But it's of no help, unfirtunately

kind regards, Ralf

[BlackDex]

Is that what you received using the Flight Recorder?
If so, it isn't very useful for me unfortunately.

All i can think of is that either the self-hosted URL is incorrect, or something is wrong with your reverse-proxy or instance.

Best is to try and fully logout, check and verify the self-hosted URL, login again, and during this specific time also check the logs of your reverse proxy and Vaultwarden to see if any traffic is even reaching your system.

[vfgKielIT]

This is not from "flightrecorder" but what you instantly get from the errormessage when you click "share error details"

I tried logging with flightrecorder, but the zipfiles it produces are not valid zipfiles, i cannot open them.

[BlackDex]

I'm not really sure then how to help.
The only thing i can suggest is to increase the log level of Vaultwarden and your reverse proxy and double check both receive a call/traffic.