# Vaultwarden keeps loading

**URL:** <https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210>\
**Category:** Help\
**Created:** [January 9, 2023, 1:58pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210 "2023-01-09T13:58:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hamza](https://avatars.discourse-cdn.com/v4/letter/h/a88e57/32.png) [@Hamza](https://vaultwarden.discourse.group/u/Hamza)\
**Post date:** [January 9, 2023, 1:58pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210/1 "2023-01-09T13:58:08Z")

</div>

Hello,

I am self hosting a Vaultwarden instance. I am running it as follows:

```auto
docker run -d --name vaultwarden -v /vw-data/:/data/ -e ROCKET_PORT=8088 -e DOMAIN=https://<MY DOMAIN> -e WEBSOCKET_ENABLED=true -p 8088:8088 -e WEBSOCKET_ADDRESS=127.0.0.1 -e DOMAIN_ORIGIN=https://<MY_DOMAIN> vaultwarden/server:latest

```

When I try accessing it through a Web browser, I get a loading page that never ends. Or a blank page with only “Bitwarden” written.  
I checked the docker logs and I get this:

```auto
/--------------------------------------------------------------------\
| Starting Vaultwarden |
| Version 1.27.0 |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the |
| official channels to report bugs/features, regardless of client. |
| Send usage/configuration questions or feature requests to: |
| https://vaultwarden.discourse.group/ |
| Report suspected bugs/issues in the software itself at: |
| https://github.com/dani-garcia/vaultwarden/issues/new |
\--------------------------------------------------------------------/

[INFO] No .env file found.

[WARNING] The following environment variables are being overriden by the config file,
[WARNING] please use the admin panel to make changes to them:
[WARNING] DOMAIN

[2023-01-09 13:51:56.557][vaultwarden::api::notifications][INFO] Starting WebSockets server on 127.0.0.1:3012
[2023-01-09 13:51:56.559][start][INFO] Rocket has launched from http://0.0.0.0:8088

```

Everything is green in the diagnostic page. The instance worked just fine until yesterday and I didn’t change anything in particular.  
Does anybody know what the problem may come from?

Thanks!

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [January 9, 2023, 2:37pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210/2 "2023-01-09T14:37:51Z")

</div>

There isn’t anything useful in the data you posted.  
Is it still not running right now? Is it still going down?

What do the logs say from Vaultwarden, Docker and your Host.  
There must be something there.

---

<div class="post-metadata">

**Author:** ![Hamza](https://avatars.discourse-cdn.com/v4/letter/h/a88e57/32.png) [@Hamza](https://vaultwarden.discourse.group/u/Hamza)\
**Post date:** [January 9, 2023, 2:52pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210/3 "2023-01-09T14:52:12Z")

</div>

The logs from Docker give me this when I try accessing my instance from a web browser:

```auto
[2023-01-09 14:49:24.053][_][WARN] Remote left: channel closed.
[2023-01-09 14:49:24.054][_][WARN] Remote left: channel closed.
[2023-01-09 14:49:24.054][_][WARN] Remote left: channel closed.

```

When I try to access my vault from the Bitwarden Android app, it opens but it appears empty (although I can see it is not from the admin panel) and I get this log from Docker:

```auto
[2023-01-09 14:46:59.188][request][INFO] GET /api/sync
[2023-01-09 14:46:59.193][response][INFO] (sync) GET /api/sync?<data..> => 200 OK

```

---

<div class="post-metadata">

**Author:** ![Hamza](https://avatars.discourse-cdn.com/v4/letter/h/a88e57/32.png) [@Hamza](https://vaultwarden.discourse.group/u/Hamza)\
**Post date:** [January 9, 2023, 6:54pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210/4 "2023-01-09T18:54:35Z")

</div>

Problem solved. It actually had nothing to do with Vaultwarden, my server ran out of disk space.  
Sorry for the useless post!

---

<div class="post-metadata">

**Author:** ![stefan0xC](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/stefan0xc/32/1765_2.png) [@stefan0xC](https://vaultwarden.discourse.group/u/stefan0xC)\
**Post date:** [January 9, 2023, 7:03pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210/5 "2023-01-09T19:03:28Z")

</div>

I don’t think it’s useless. It may help us diagnose the problem when others have the same issue. 👍

---

<div class="post-metadata">

**Author:** ![serega404](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/serega404/32/1065_2.png) [@serega404](https://vaultwarden.discourse.group/u/serega404)\
**Post date:** [April 18, 2023, 2:06pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210/6 "2023-04-18T14:06:51Z")

</div>

Your question helped me a lot! My nginx server ran out of memory so I got the same problem

---

<div class="post-metadata">

**Author:** ![mattmontanez](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@mattmontanez](https://vaultwarden.discourse.group/u/mattmontanez)\
**Post date:** [June 4, 2023, 4:53pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210/7 "2023-06-04T16:53:18Z")

</div>

This was the answer to my problem. Thanks so much for posting the answer to fix this!