mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-17 20:30:22 -05:00
Takes a long time to load on Ubuntu 19.10 #621
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @uchagani on GitHub (Feb 25, 2020).
Subject of the issue
bitwarden_rs takes a long time to load on Ubuntu 19.10.
Your environment
Steps to reproduce
On Ubuntu 19.10 run
docker run -d --name bitwarden -v /home/umair/bw-data/:/data/ -p 8080:80 -e LOG_FILE=/data/bitwarden.log -e EXTENDED_LOGGING=true -e LOG_LEVEL=trace bitwardenrs/server:latestOpen firefox to your
http://ipaddress:8080Expected behaviour
Bitwarden should load as normal
Actual behaviour
Logo is shown and bitwarden takes 10min to load.
Image:

Relevant logs
I upped the log level to
trace@jjlin commented on GitHub (Feb 25, 2020):
Try adding
-e DOMAIN=http://ipaddress:8080to yourdocker run@uchagani commented on GitHub (Feb 25, 2020):
doesn't help. i removed the container and reran it with
-e DOMAIN=http://192.168.xxx.xxx:8080Log file just keeps repeating this:
@jjlin commented on GitHub (Feb 25, 2020):
Try opening the browser dev tools (usually pressing F12 works) and go to the network tab to see what requests are getting stuck or failing. You may have to reload the page to see it.
@uchagani commented on GitHub (Feb 25, 2020):
All the other requests took between 3-8 seconds except for the initial request. I double checked..it's seconds not milliseconds.
@jjlin commented on GitHub (Feb 25, 2020):
Anything special about the networking between your computer and the Docker host? It seems it's very slow for some reason.
@uchagani commented on GitHub (Feb 25, 2020):
Not that I think. Here are some results from iperf3 between the docker host and my laptop where i'm accessing bitwarden from.
@uchagani commented on GitHub (Feb 25, 2020):
I wanted to make sure there was nothing funky going on from within docker so on my docker host I removed iperf3 and ran iperf3 via docker using the image
networkstatic/iperf3. Connected to this via my laptop again and the results are below:@uchagani commented on GitHub (Feb 26, 2020):
this seemed to be an issue with one of my NICs.