starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-25 17:25:57 +03:00

[GH-ISSUE #993] Bitwarden RS container hangs when is not allowed to access the Internet #705

New issue

Closed

opened 2026-03-03 02:02:22 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 02:02:22 +03:00

Owner

Originally created by @ajgon on GitHub (May 13, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/993

Subject of the issue

So here is the problem. I run my personal home-lab with plenty of services. To prevent them from "calling home" default policy for containers is to disallow any access to the Internet. However since I have problem with "internal loopbacks" with bitwarden and some other apps, containers can access themselves using their own domain name (so bitwarden.example.com can access any endpoint using bitwarden.example.com/something without any problem).

This setup worked flawlessly until recently. When I try to create a new item, Bitwarden hangs. When I enable access to the Internet, everything works as expected.

It happens both in OSX client and in web interface.

Your environment

Bitwarden_rs version: 1.14.2-8bbbff75
Install method: Docker
Clients used: OSX, web
Reverse proxy and version: nginx 1.17.9
Version of mysql/postgresql: Postgres 12.2
Other relevant information:

Steps to reproduce

Set up bitwarden_rs docker container
Disable Internet access to the container (create network with --internal param and attach it as a only network)
Access web panel and try to save an item

Expected behaviour

Item should be saved properly.

Actual behaviour

Bitwarden container hangs.

Relevant logs

Nothing extraordinary except failed icons download (which is expected as container has no access to the Internet):

May 13 18:56:11 deedee bitwarden[560]: [2020-05-13 18:56:11][bitwarden_rs::api::icons][INFO] Download failed for https://****/favicon.ico
May 13 18:56:11 deedee bitwarden[560]: [2020-05-13 18:56:11][bitwarden_rs::api::icons][INFO] Download failed for https://****/favicon.ico
May 13 18:56:11 deedee bitwarden[560]: [2020-05-13 18:56:11][bitwarden_rs::api::icons][INFO] Download failed for https://****/favicon.ico
...

I really appreciate any help - should I allow some extra domains, or is it related to something else?

Thanks!

Originally created by @ajgon on GitHub (May 13, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/993 ### Subject of the issue So here is the problem. I run my personal home-lab with plenty of services. To prevent them from "calling home" default policy for containers is to disallow any access to the Internet. However since I have problem with "internal loopbacks" with bitwarden and some other apps, containers can access themselves using their own domain name (so `bitwarden.example.com` can access any endpoint using `bitwarden.example.com/something` without any problem). This setup worked flawlessly until recently. When I try to create a new item, Bitwarden hangs. When I enable access to the Internet, everything works as expected. It happens both in OSX client and in web interface. ### Your environment * Bitwarden_rs version: 1.14.2-8bbbff75 * Install method: Docker * Clients used: OSX, web * Reverse proxy and version: nginx 1.17.9 * Version of mysql/postgresql: Postgres 12.2 * Other relevant information: ### Steps to reproduce * Set up bitwarden_rs docker container * Disable Internet access to the container (create network with `--internal` param and attach it as a only network) * Access web panel and try to save an item ### Expected behaviour Item should be saved properly. ### Actual behaviour Bitwarden container hangs. ### Relevant logs Nothing extraordinary except failed icons download (which is expected as container has no access to the Internet): ``` May 13 18:56:11 deedee bitwarden[560]: [2020-05-13 18:56:11][bitwarden_rs::api::icons][INFO] Download failed for https://****/favicon.ico May 13 18:56:11 deedee bitwarden[560]: [2020-05-13 18:56:11][bitwarden_rs::api::icons][INFO] Download failed for https://****/favicon.ico May 13 18:56:11 deedee bitwarden[560]: [2020-05-13 18:56:11][bitwarden_rs::api::icons][INFO] Download failed for https://****/favicon.ico ... ``` I really appreciate any help - should I allow some extra domains, or is it related to something else? Thanks!

kerem closed this issue

2026-03-03 02:02:22 +03:00

kerem commented

2026-03-03 02:02:23 +03:00

Author

Owner

@mqus commented on GitHub (May 13, 2020):

Hey! thanks for the report!
Did you try to disable Icon downloading? (using the environment variable, see https://github.com/dani-garcia/bitwarden_rs/blob/master/.env.template#L71) I think bitwarden_rs should not hang even if it isn't disabled but maybe that helps in you case?

@mqus commented on GitHub (May 13, 2020): Hey! thanks for the report! Did you try to disable Icon downloading? (using the environment variable, see https://github.com/dani-garcia/bitwarden_rs/blob/master/.env.template#L71) I think bitwarden_rs should not hang even if it isn't disabled but maybe that helps in you case?

kerem commented

2026-03-03 02:02:23 +03:00

Author

Owner

@ajgon commented on GitHub (May 13, 2020):

Ha! My initial idea was to disable that, but wasn't aware of the option. After disabling it, everything went back to normal.

Thank you!

@ajgon commented on GitHub (May 13, 2020): Ha! My initial idea was to disable that, but wasn't aware of the option. After disabling it, everything went back to normal. Thank you!

kerem commented

2026-03-03 02:02:23 +03:00

Author

Owner

@dani-garcia commented on GitHub (May 13, 2020):

I assume the hang is caused by the server trying to connect and waiting on a timeout, which by default is 10 seconds. The version of rocket that we currently use has a fixed number of threads, so once all of them are saturated waiting on a timeout the server will hang. This is particularly bad when a client has a lot of ciphers with a lot of icons.

That said, yeah in your case disabling them is the correct choice, so this can be closed.

@dani-garcia commented on GitHub (May 13, 2020): I assume the hang is caused by the server trying to connect and waiting on a timeout, which by default is 10 seconds. The version of rocket that we currently use has a fixed number of threads, so once all of them are saturated waiting on a timeout the server will hang. This is particularly bad when a client has a lot of ciphers with a lot of icons. That said, yeah in your case disabling them is the correct choice, so this can be closed.

kerem referenced this issue

2026-03-03 08:53:05 +03:00

[PR #713] [MERGED] Fixed issue/request #705 #2788