search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
4.55k stars 937 forks source link

Web interface unresponsive when Bitwarden Extension is installed (Chrome/Chromium) #3419

Closed c11umw closed 2 weeks ago

c11umw commented 2 weeks ago

Describe the issue you are experiencing

I recently set up a self-hosted VaultWarden (not BitWarden) for the first time. We never used a Bitwarden/Vaultwarden before, so the content was fresh.

Once it was all set up I installed the Bitwarden Extension to use in Chrome and then noticed that HomeAssistant pages became unresponsive and after a while a Chrome pop-up would show with an Unresponsive Alert message: image

All other sites were navigating fine, so I tried clearing cookies and cache, restarting the PC and nothing resolved the issue. Then I disabled the extension and opened HomeAssistant in a new tab and it was immediately fast and responsive again. It seems that, even if Bitwarden is active and not displayed in the toolbar it still affects HomeAssistant.

Tested with a fresh and empty HomeAssistant HAOS in Proxmox VM and it also "hung" that fresh install. The pop-up message auto-clears (unlike my live HomeAssistant), but there's still the 30s delay with the site hanging until the pop-up shows.

Tested with Firefox and Bitwarden extension installed and there's no slowdown. Tested with Edge and it hung the same as Chrome, so HAOS seems to only be affected when used in a Chromium based browser

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

6.6.29-haos

Did the problem occur after upgrading the Operating System?

No

Hardware details

Proxmox 8.2.2 VM on Lenovo Tiny PC (Intel i5-4590T. 4 core, 500Gb disk, 16Gb Ram) Assigned: 128Gb disk, 8Gb Ram, 4 cores.

Steps to reproduce the issue

  1. Install Vaultwarden for self hosted passwords
  2. Install and activate Bitwarden Extension in Chrome (doesn't matter if logged in or not)
  3. Choose SelfHosted and setup HTTPS URL and log in.
  4. Try to navigate Home Assistant pages

Anything in the Supervisor logs that might be useful for us?

no entries when testing

Anything in the Host logs that might be useful for us?

no entries when testing

System information

System Information

version core-2024.6.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.6.29-haos
arch x86_64
timezone Africa/Lagos
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1457 Downloaded Repositories | 50
Home Assistant Cloud logged_in | true -- | -- subscription_expiration | 1 January 2018 at 00:00 relayer_connected | false relayer_region | null remote_enabled | false remote_connected | false alexa_enabled | false google_enabled | false remote_server | null certificate_status | null instance_id | 33666b5ca6244ca6a2c33a8fd1787380 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 12.3 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.0 agent_version | 1.6.0 docker_version | 25.0.5 disk_total | 125.3 GB disk_used | 18.1 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | kvm board | ova supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (18.0.0), Cloudflared (5.1.12), DHCP server (1.4.0), Home Assistant Google Drive Backup (0.112.1), chrony (3.0.1), Log Viewer (0.17.0), MariaDB (2.7.1), Mosquitto broker (6.4.1), Studio Code Server (5.15.0), Samba share (12.3.1), Tailscale (0.20.0), RPC Shutdown (2.5), SQLite Web (4.1.2), Uptime Kuma (0.12.1)
Dashboards dashboards | 7 -- | -- resources | 30 views | 39 mode | storage
Miele component_version | 2024.5.0 -- | -- reach_miele_cloud | ok
Recorder oldest_recorder_run | 17 May 2024 at 14:53 -- | -- current_recorder_run | 16 June 2024 at 01:22 estimated_db_size | 5529.84 MiB database_engine | mysql database_version | 10.11.6
Sonoff version | 3.7.3 (e240aaf) -- | -- cloud_online | 0 / 3 local_online | 3 / 3

Additional information

Docker CLI for Vaultwarden. Running as non-root user:

docker run -d \
--name=vaultwarden \
-p 80:80 \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-e WEB_VAULT_ENABLED=true \
-e SIGNUPS_ALLOWED=false \
-e SIGNUPS_DOMAINS_WHITELIST=domain1.co.uk,domain2.com,domain3.com \
-e ORG_CREATION_USERS=onlymy@account.com \
-e DOMAIN=https://mydomain.url \
-e LOG_LEVEL=error \
-v /home/nonrootuser/data/vaultwarden:/data/ \
--restart=always \
vaultwarden/server:latest
github-actions[bot] commented 2 weeks ago

:wave: @c11umw, thanks for reporting an issue!

It looks like this issue is related to Home Assistant Frontend. Please check the Home Assistant Frontend repository, the issue might have been reported already. Open a new issue in that repository if you can't find a matching issue.

c11umw commented 2 weeks ago

Resolved following Bitwarden update ( https://github.com/home-assistant/frontend/issues/21101 )