BitWarden not responding after short period of time | Self Hosted

Ask the Community Password Manager
,
1

Hi everyone,
a few weeks ago I deployed BitWarden self-hosted for my organization on Windows via Docker. The Server its running on is only reachable in our intern network and this works fine.

But after one or two days my Bitwarden instance becommes unreachable. Even when loggin in through the browser on the server, I get a “Fetch failed” Error. The docker UI and the command line both print a cryptic error message, something about docker engine being unreachable and the container not being found (even when clicking “stop” on the running container).

Sometimes a restart of the server resolves the issue, but most of the time I need to manually kill all running docker tasks with my taskmanager. There often multiple (10 or more) instances of Docker are running at the same time.

Has anyone else encountered something similar or has any idea, how I can solve or maybe even further localise my problem? Many thanks in advance.

2

I wonder if your issue is the same as mine - Unhealthy containers - normal for a self-hosted install with no Internet access?
Mine is running on a Ubuntu platform, but both your and my install have no Internet access and I wonder if this is the problem.
I’m not familiar with Docker on Windows, but is there an equivalent for docker ps ? If so, you might find they’re all unhealthy (apart from possibly the SQL).

3

Hi, thank you for your reply. I used your suggested command, but it shows all containers as “healthy”, leading me to believe, we might have different problems.