[GH-ISSUE #1104] Freezing when unable to resolve DNS #782

New issue

Closed

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

kerem commented

2026-03-03 02:03:09 +03:00

Owner

Originally created by @sfkpmr on GitHub (Aug 17, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1104

I'm having an odd issue on my Docker host that makes containers unable to resolve DNS, but as my containers don't need internet access, they generally work fine, with the exception of Bitwarden_rs.

Subject of the issue

Sometimes when using the web UI to add/remove/change entries the page loads for several minutes, and reloading the page doesn't work either. After a few minutes it continues to work normally.

Your environment

Bitwarden_rs version: 2.15.1
Install method: Docker image
Clients used: Web UI
Reverse proxy and version: Caddy v1.0.3
Version of mysql/postgresql:
Other relevant information:

Steps to reproduce

Sign in to web UI
Delete an entry.

Docker start bitwarden

Expected behaviour

Entries are updated immediately. Display DNS error in log and stop updating for some amount of time.

Actual behaviour

Load icon spins around for several minutes.

Relevant logs

It seems like updating entries triggers an update of favicons like this:

[2020-08-17 17:11:12.818][bitwarden_rs::api::icons][INFO] Download failed for https://*.com/favicon.ico
[2020-08-17 17:11:12.824][bitwarden_rs::api::icons][INFO] Download failed for https://*.com/favicon.ico
[2020-08-17 17:11:12.824][bitwarden_rs::api::icons][INFO] Download failed for https://*.com/favicon.ico
[2020-08-17 17:11:41.985][bitwarden_rs::api::icons][INFO] Download failed for http://www.*.com/favicon.ico
[2020-08-17 17:11:41.985][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response
[2020-08-17 17:11:41.985][response][INFO] GET /icons/<domain>/icon.png (icon) => 200 OK
[2020-08-17 17:11:42.007][bitwarden_rs::api::icons][INFO] Download failed for http://*.com/favicon.ico
[2020-08-17 17:11:42.007][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response
[2020-08-17 17:11:42.007][response][INFO] GET /icons/<domain>/icon.png (icon) => 200 OK
[2020-08-17 17:11:42.048][bitwarden_rs::api::icons][INFO] Download failed for http://*.com/favicon.ico
[2020-08-17 17:11:42.048][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response
[2020-08-17 17:11:42.048][response][INFO] GET /icons/<domain>/icon.png (icon) => 200 OK

Originally created by @sfkpmr on GitHub (Aug 17, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1104 I'm having an odd issue on my Docker host that makes containers unable to resolve DNS, but as my containers don't need internet access, they generally work fine, with the exception of Bitwarden_rs. ### Subject of the issue Sometimes when using the web UI to add/remove/change entries the page loads for several minutes, and reloading the page doesn't work either. After a few minutes it continues to work normally. ### Your environment  * Bitwarden_rs version: 2.15.1 * Install method: Docker image * Clients used: Web UI * Reverse proxy and version:  Caddy v1.0.3 * Version of mysql/postgresql:  * Other relevant information: ### Steps to reproduce  1. Sign in to web UI 2. Delete an entry. Docker start bitwarden ### Expected behaviour  Entries are updated immediately. Display DNS error in log and stop updating for some amount of time. ### Actual behaviour  Load icon spins around for several minutes. ### Relevant logs  It seems like updating entries triggers an update of favicons like this: ``` [2020-08-17 17:11:12.818][bitwarden_rs::api::icons][INFO] Download failed for https://*.com/favicon.ico [2020-08-17 17:11:12.824][bitwarden_rs::api::icons][INFO] Download failed for https://*.com/favicon.ico [2020-08-17 17:11:12.824][bitwarden_rs::api::icons][INFO] Download failed for https://*.com/favicon.ico [2020-08-17 17:11:41.985][bitwarden_rs::api::icons][INFO] Download failed for http://www.*.com/favicon.ico [2020-08-17 17:11:41.985][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response [2020-08-17 17:11:41.985][response][INFO] GET /icons/<domain>/icon.png (icon) => 200 OK [2020-08-17 17:11:42.007][bitwarden_rs::api::icons][INFO] Download failed for http://*.com/favicon.ico [2020-08-17 17:11:42.007][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response [2020-08-17 17:11:42.007][response][INFO] GET /icons/<domain>/icon.png (icon) => 200 OK [2020-08-17 17:11:42.048][bitwarden_rs::api::icons][INFO] Download failed for http://*.com/favicon.ico [2020-08-17 17:11:42.048][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response [2020-08-17 17:11:42.048][response][INFO] GET /icons/<domain>/icon.png (icon) => 200 OK ```

kerem closed this issue

2026-03-03 02:03:10 +03:00

kerem commented

2026-03-03 02:03:11 +03:00

Author

Owner

@mqus commented on GitHub (Aug 18, 2020):

You can disable the icon loading in the configuration/via an environment variable
github.com/dani-garcia/bitwarden_rs@eba22c2d94/.env.template (L85-L89)

This should be the only external request that needs DNS (apart from maybe sending email, depending on your configuration).

@mqus commented on GitHub (Aug 18, 2020): You can disable the icon loading in the configuration/via an environment variable https://github.com/dani-garcia/bitwarden_rs/blob/eba22c2d9429b9f9bad5baff9b1d571b469645c9/.env.template#L85-L89 This should be the only external request that needs DNS (apart from maybe sending email, depending on your configuration).

kerem commented

2026-03-03 02:03:11 +03:00

Author

Owner

@sfkpmr commented on GitHub (Aug 18, 2020):

Thanks, that might have done it! Should probably wait a bit to make sure though.

Ideally though you shouldn't need to disable the icon download though. The UI shouldn't freeze up if the DNS is temporarily down for example.

@sfkpmr commented on GitHub (Aug 18, 2020): Thanks, that might have done it! Should probably wait a bit to make sure though. Ideally though you shouldn't need to disable the icon download though. The UI shouldn't freeze up if the DNS is temporarily down for example.

kerem commented

2026-03-03 02:03:11 +03:00

Author

Owner

@BlackDex commented on GitHub (Sep 1, 2020):

That will partially be fixed when we can go to async http server. But still it would slow down since the icons are fetched by the web-vault unless you disable it.

There is also an option to disable this in your account within the web-vault, this should prevent calls to the server it self at all. Same goes for the mobile clients.

@BlackDex commented on GitHub (Sep 1, 2020): That will partially be fixed when we can go to async http server. But still it would slow down since the icons are fetched by the web-vault unless you disable it. There is also an option to disable this in your account within the web-vault, this should prevent calls to the server it self at all. Same goes for the mobile clients.