Problem/Motivation

The web vault shows empty even for folders - it seems with a high volume of passwords (>3000 in my case) - but even folders with as little as 15 now dont show any passwords

Expected behavior

being able to see all password as they are shown on the desktop and iOS app after sync

Actual behavior

vault looks empty shows: "There are no items to list." even when selecting a folder - tried different browsers, FF, Safari, Chrome

Chrome also shows errors:

WebSocketTransport.js:85 WebSocket connection to 'wss://A.B.C.D:7277/notifications/hub?id=[ID]==&access_token=[removed]' failed: Error during WebSocket handshake: Unexpected response code: 400

Utils.js:203 [2019-12-09T13:05:36.969Z] Error: Failed to start the transport 'WebSockets': null

[2019-12-09T13:05:36.970Z] Error: Failed to start the connection: Error: Unable to initialize any of the available transports

Steps to reproduce

inset large list of passwords then sync them to different devices - devices desktop, mobile works and shows all data - web wont

Proposed changes

investigate issue

After I installed the Addon and changed the admin password I tried to open the vault but it shows only this:

��9� ���z}Vh�9��� XS���9�IW�4�b���H��#�8��e��kD�F>[�D���H���H��_SOURCE_REALTIME_TIMESTAMP=1594864032156286�������#�8���9y�l��t8�ƃA�[�Z���m��,{|P��8�&��������8�4���ev�p�8�:�Z-�U���8d;�ߝ]���8���n�s�݀�8�!+�6�}���8��g�������8*���3 :_�8I�lS4��9��8�y�����Qh�8 L�8M�ތ��82uW����.X9���l�g���9c����6�G�9���+�{�X@�9�0O�È� ��9c�y�FW%���9�������^��9o����PX���9׋�Y��!� �9q�_ܸ@���9� ���z}Vh�9��� XS�@�H�D�F>[�D��k�=�.w{g��>�@�H��H��_SOURCE_REALTIME_TIMESTAMP=1594864032156323�������%�8���dz�l��t8�ƃA�[�Z���

This is my config:
ssl: true certfile: fullchain.pem keyfile: privkey.pem log_level: debug

This is the addon log:
[2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/<uuid>/collections-admin [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/<uuid>/delete [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/<uuid>/delete-admin [2020-08-19 23:02:38][routes][INFO] GET /api/ciphers/<uuid>/details [2020-08-19 23:02:38][routes][INFO] PUT /api/ciphers/<uuid>/share [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/<uuid>/share [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/admin [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/create [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/delete [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/import [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/import-organization?<query..> [2020-08-19 23:02:38][routes][INFO] PUT /api/ciphers/move [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/move [2020-08-19 23:02:38][routes][INFO] GET /api/ciphers/organization-details?<data..> [2020-08-19 23:02:38][routes][INFO] POST /api/ciphers/purge?<organization..> [2020-08-19 23:02:38][routes][INFO] PUT /api/ciphers/share [2020-08-19 23:02:38][routes][INFO] GET /api/collections [2020-08-19 23:02:38][routes][INFO] PUT /api/devices/identifier/<uuid>/clear-token [2020-08-19 23:02:38][routes][INFO] PUT /api/devices/identifier/<uuid>/token [2020-08-19 23:02:38][routes][INFO] GET /api/folders [2020-08-19 23:02:38][routes][INFO] POST /api/folders [2020-08-19 23:02:38][routes][INFO] DELETE /api/folders/<uuid> [2020-08-19 23:02:38][routes][INFO] PUT /api/folders/<uuid> [2020-08-19 23:02:38][routes][INFO] GET /api/folders/<uuid> [2020-08-19 23:02:38][routes][INFO] POST /api/folders/<uuid> [2020-08-19 23:02:38][routes][INFO] POST /api/folders/<uuid>/delete [2020-08-19 23:02:38][routes][INFO] GET /api/hibp/breach?<username> [2020-08-19 23:02:38][routes][INFO] POST /api/organizations [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<_org_id>/users/<_org_user_id>/accept [2020-08-19 23:02:38][routes][INFO] DELETE /api/organizations/<org_id> [2020-08-19 23:02:38][routes][INFO] PUT /api/organizations/<org_id> [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id> [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id> [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id>/collections [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/collections [2020-08-19 23:02:38][routes][INFO] DELETE /api/organizations/<org_id>/collections/<col_id> [2020-08-19 23:02:38][routes][INFO] PUT /api/organizations/<org_id>/collections/<col_id> [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/collections/<col_id> [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/collections/<col_id>/delete [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/collections/<col_id>/delete-user/<org_user_id> [2020-08-19 23:02:38][routes][INFO] DELETE /api/organizations/<org_id>/collections/<col_id>/user/<org_user_id> [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id>/collections/<coll_id>/details [2020-08-19 23:02:38][routes][INFO] PUT /api/organizations/<org_id>/collections/<coll_id>/users [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id>/collections/<coll_id>/users [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/delete [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/leave [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id>/policies [2020-08-19 23:02:38][routes][INFO] PUT /api/organizations/<org_id>/policies/<pol_type> [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id>/policies/<pol_type> [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id>/policies/token?<token> [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id>/users [2020-08-19 23:02:38][routes][INFO] DELETE /api/organizations/<org_id>/users/<org_user_id> [2020-08-19 23:02:38][routes][INFO] PUT /api/organizations/<org_id>/users/<org_user_id> [1] [2020-08-19 23:02:38][routes][INFO] GET /api/organizations/<org_id>/users/<org_user_id> [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/users/<org_user_id> [1] [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/users/<org_user_id>/confirm [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/users/<org_user_id>/delete [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/users/<user_org>/reinvite [2020-08-19 23:02:38][routes][INFO] POST /api/organizations/<org_id>/users/invite [2020-08-19 23:02:38][routes][INFO] PUT /api/settings/domains [2020-08-19 23:02:38][routes][INFO] GET /api/settings/domains [2020-08-19 23:02:38][routes][INFO] POST /api/settings/domains [2020-08-19 23:02:38][routes][INFO] GET /api/sync?<data..> [2020-08-19 23:02:38][routes][INFO] GET /api/two-factor [2020-08-19 23:02:38][routes][INFO] PUT /api/two-factor/authenticator [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/authenticator [2020-08-19 23:02:38][routes][INFO] PUT /api/two-factor/disable [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/disable [2020-08-19 23:02:38][routes][INFO] PUT /api/two-factor/duo [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/duo [2020-08-19 23:02:38][routes][INFO] PUT /api/two-factor/email [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/get-authenticator [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/get-duo [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/get-email [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/get-recover [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/get-u2f [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/get-u2f-challenge [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/get-yubikey [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/recover [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/send-email [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/send-email-login [2020-08-19 23:02:38][routes][INFO] DELETE /api/two-factor/u2f [2020-08-19 23:02:38][routes][INFO] PUT /api/two-factor/u2f [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/u2f [2020-08-19 23:02:38][routes][INFO] PUT /api/two-factor/yubikey [2020-08-19 23:02:38][routes][INFO] POST /api/two-factor/yubikey [2020-08-19 23:02:38][routes][INFO] GET /api/users/<uuid>/public-key [2020-08-19 23:02:38][routes][INFO] GET /app-id.json [2020-08-19 23:02:38][routes][INFO] GET /attachments/<uuid>/<file..> [2020-08-19 23:02:38][routes][INFO] GET /bwrs_static/<filename> [2020-08-19 23:02:38][routes][INFO] GET /icons/<domain>/icon.png [2020-08-19 23:02:38][routes][INFO] POST /identity/connect/token [2020-08-19 23:02:38][routes][INFO] GET /notifications/hub [2020-08-19 23:02:38][routes][INFO] POST /notifications/hub/negotiate [2020-08-19 23:02:38][start][INFO] Rocket has launched from http://0.0.0.0:80 [23:02:38] INFO: Starting NGinx... [2020-08-19 23:17:14][request][INFO] GET / [2020-08-19 23:17:14][response][INFO] GET / (web_index) => 200 OK [19/Aug/2020:23:17:14 +0200] 200 -(192.168.86.1) GET / HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.125 Safari/537.36) [19/Aug/2020:23:17:25 +0200] 400 -(193.142.146.50) \x03\x00\x00/*\xE0\x00\x00\x00\x00\x00Cookie: mstshash=Administr (-)

No updates in 6 months, for a product that secures passwords this seems dangerous to keep running without updates.

Motivation

I would be nice if Yubico Keys were supported in the hassio addon version. For that bitwarden_rs needs some enviroment variables. I don't know how (or if it is possible) to pass these in the hassio configuration

Steps to reproduce

If i want to add a Yubico Key the following error message occurs:

`YUBICO_CLIENT_ID` or `YUBICO_SECRET_KEY` environment variable is not set. Yubikey OTP Disabled

Proposed changes

add config for these enviroment vars:

• YUBICO_CLIENT_ID
• YUBICO_SECRET_KEY

Further recources:

https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-Yubikey-OTP-authentication

GitHub

dani-garcia/bitwarden_rs

Unofficial Bitwarden compatible server written in Rust - dani-garcia/bitwarden_rs

Hi! I'd like to be able to change some environment variables at startup and I was wondering if said functionality would be appreciated when offered as a PR.

Preferably I add a list of env vars that can be set in the configuration as is done in (for example) the grafana addon.

When I add this feature to the addon, would you merge it or is it something I'd better use just in my own fork?

Problem/Motivation

Currently the version cannot be upgraded because because of the way multiarch got introduced by bitwarden and the way the build of this addon is done.
Example of the failure signature from last ci results:

manifest for bitwardenrs/server:1.16.0-aarch64 not found: manifest unknown: manifest unknown

Proposed changes

Franck do you think migrating to use buildx with dind (docker in docker) as described in https://www.docker.com/blog/multi-arch-build-what-about-gitlab-ci/ is a viable solution?

I noticed that there is already some configuration in https://github.com/hassio-addons/organization/blob/master/gitlabci/addon.yml#L65-L73 that mentions dind is it possible to fetch buildx and change the build step (https://github.com/jdrouet/docker-on-ci/blob/master/Makefile#L7-L9)?

Problem/Motivation

In the tools section of bitwarden I can't click on the weak password report without the website crashing. All other tools on this site (reused passwords, etc.) work totally fine, just this feature seem to break in my browser. The site will hang there until I close it, all other buttons on the website aren't working either from that moment on until reopening the page.

Steps to reproduce

I am using Firefox 84.0.2 and run the current version 0.7.0 of this addon.

Proposed changes

I don't really know why this is happening because I am also running another Bitwarden instance seperatly with the current Docker image from Docker Hub and there isn't this problem.

Problem/Motivation

Be able to set SMTP server to send invite to users

Expected behavior

A mail to be sent to users

Actual behavior

Could not find where to setup the SMTP server parameters as per https://github.com/dani-garcia/bitwarden_rs/wiki/SMTP-configuration - Where are those?

Steps to reproduce

See above

Proposed changes

See above

Have probems with latest iOS and Self hosting Bitwarden:

(Saw this on the community site of Bitwarden)
Hi There! First of all love the app and being able to host my own server!

So recently (I don’t know how recent) I’ve been having issues with my iPhone Bitwarden App.

I cannot just unlock the app with my master password. It says “Invalid Master Password. Try Again”. Basically I have to fully logout of the app and then re-login in order to access my passwords. I have confirmed I’m using the correct login and password. Also the option with the integration in the keyboard to access bitwarden will not work. It has the same message when I try to access my vault from the keyboard.

I have tried deleting/logging out then in, and restarted my phone but still it has the same behavior.

Anyone experience this? And if so, have they been able to resolve it?

Thanks!

Answer:
Make sure your server is running the latest version (1.38.4) as there are new pieces of information in the API that the client apps need to unlock correctly.

Problem/Motivation

I currently run bitwarden_rs on a different server and would like to use this as a backup/emergency server. I would like to automatically sync my db.sqlite3, config.json, and RSA key files between the servers so that I will always have a server available. The failover is out of scope of this addon, but it will be handled either by my current HTTPS reverse proxy automatically, or I'll make the change manually.

Proposed changes

Ideally, the bitwarden_rs /data directory could be exposed as a folder to the default /addons directory exposed through the hassio Samba share.

This would allow me to sync my vault as well as offer others the ability to manually backup their bitwarden_rs data for safe keeping. I don't believe there is any security implications as everything is well encrypted, but perhaps this could be a config option for those that choose not to do it.

I believe I could use Portainer to map it manually but doing it each time there is an upgrade would be challenging. And using this addon without the ability to make a manual backup for safekeeping worries me, so I don't know that I could use it as a primary server (or recommend it to others) until it's possible.

The errorr comes when I go on 127.0.0.1;7277 and enter my credentials

/--------------------------------------------------------------------
| Starting Bitwarden_RS |

[2019-05-09 09:32:00][launch][INFO] Configured for production.
[2019-05-09 09:32:00][launch_][INFO] address: 0.0.0.0
[2019-05-09 09:32:00][launch_][INFO] port: 7277
[2019-05-09 09:32:00][launch_][INFO] log: critical
[2019-05-09 09:32:00][launch_][INFO] workers: 2
[2019-05-09 09:32:00][launch_][INFO] secret key: provided
[2019-05-09 09:32:00][launch_][INFO] limits: forms = 32KiB, json* = 10MiB
[2019-05-09 09:32:00][launch_][INFO] keep-alive: 5s
[2019-05-09 09:32:00][launch_][INFO] tls: disabled
[2019-05-09 09:32:00][rocket::fairing::fairings][INFO] Fairings:
[2019-05-09 09:32:00][][INFO] 1 response: Application Headers
[2019-05-09 09:32:00][launch][INFO] Rocket has launched from http://0.0.0.0:7277
[2019-05-09 09:32:11][rocket::rocket][INFO] GET / text/html:
[2019-05-09 09:32:11][][INFO] Matched: GET / (web_index)
[2019-05-09 09:32:11][][INFO] Outcome: Success
[2019-05-09 09:32:11][][INFO] Response succeeded.
[2019-05-09 09:32:11][rocket::rocket][INFO] GET /app/main.5d89a1c78e2fbd6f2ec5.css text/css:
[2019-05-09 09:32:11][][INFO] Matched: GET /<p..> [10] (web_files)
[2019-05-09 09:32:11][][INFO] Outcome: Success
[2019-05-09 09:32:11][][INFO] Response succeeded.
[2019-05-09 09:32:11][rocket::rocket][INFO] GET /locales/it/messages.json?cache=1dqoka:
[2019-05-09 09:32:11][][INFO] Matched: GET /<p..> [10] (web_files)
[2019-05-09 09:32:11][][INFO] Outcome: Success
[2019-05-09 09:32:11][][INFO] Response succeeded.
[2019-05-09 09:32:12][rocket::rocket][INFO] GET /locales/en/messages.json?cache=1dqoka:
[2019-05-09 09:32:12][][INFO] Matched: GET /<p..> [10] (web_files)
[2019-05-09 09:32:12][][INFO] Outcome: Success
[2019-05-09 09:32:12][][INFO] Response succeeded.
[2019-05-09 09:32:18][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8:
[2019-05-09 09:32:18][][INFO] Matched: POST /api/accounts/prelogin (prelogin)
[2019-05-09 09:32:18][][INFO] Outcome: Success
[2019-05-09 09:32:18][][INFO] Response succeeded.

The installation section says:
Check the logs of the "Bitwarden RS" add-on to see if everything went well and to get the admin token / password.
For some reason, at the moment I do not have an access token to the admin panel in the log. Previously, I found it and used it several times, but at some point it was not there.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Bitwarden RS
 Open source password management solution
-----------------------------------------------------------
 Add-on version: 0.7.0
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 10 (buster)  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.2.1
 Home Assistant Supervisor: 2021.01.7
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[12:25:52] INFO: Starting the Bitwarden RS server...
/--------------------------------------------------------------------\
|                       Starting Bitwarden_RS                        |
|                           Version 1.18.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://bitwardenrs.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/bitwarden_rs/issues/new           |
\--------------------------------------------------------------------/
[INFO] No .env file found.
[2021-02-07 12:25:52.626][parity_ws][INFO] Listening for new connections on 0.0.0.0:8080.
[2021-02-07 12:25:52.629][start][INFO] Rocket has launched from http://0.0.0.0:80
[12:25:52] INFO: Starting NGinx...
[2021-02-07 13:26:20.973][request][INFO] POST /identity/connect/token
[2021-02-07 13:26:21.062][response][INFO] POST /identity/connect/token (login) => 200 OK
[07/Feb/2021:13:26:21 +0300] 200 -(178.155.6.10) POST /identity/connect/token HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36)
[2021-02-07 13:26:21.170][request][INFO] GET /api/sync
[2021-02-07 13:26:21.285][response][INFO] GET /api/sync?<data..> (sync) => 200 OK
[07/Feb/2021:13:26:21 +0300] 200 -(178.155.6.10) GET /api/sync HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36)
[2021-02-07 14:33:08.339][request][INFO] POST /identity/connect/token
[2021-02-07 14:33:08.358][response][INFO] POST /identity/connect/token (login) => 200 OK
[07/Feb/2021:14:33:08 +0300] 200 -(192.168.1.1) POST /identity/connect/token HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36)
[2021-02-07 14:33:08.379][request][INFO] GET /api/accounts/revision-date
[2021-02-07 14:33:08.380][response][INFO] GET /api/accounts/revision-date (revision_date) => 200 OK
[07/Feb/2021:14:33:08 +0300] 200 -(192.168.1.1) GET /api/accounts/revision-date HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36)

Problem/Motivation

Can't create user in the Bitwarden UI

Expected behavior

User to be created when you hit the submit button on the create user form

Actual behavior

Nothing, I click submit and nothing happens, there are no logs generated so can't really offer up more information

Steps to reproduce

Deploy add on as described, go to initial log on screen, go to create user and attempt to create user

Proposed changes

None as I can't fathom why it isn't working

Hi,

it is possible to specify these variables:

SIGNUPS_ALLOWED false

I have bitwarden open to the outside.
but now anyone can create bitwarden vaults.

this is no longer possible with these variables.
no idea if this is possible.

Problem/Motivation

Hi, I've installed the addon. It is running but I cannot access the UI. The log is completely empty.
Any ideas?

Regards, Tom

Expected behavior

UI

Actual behavior

Nothing

Steps to reproduce

Just installed and started it.
(also restarted PI)

Proposed changes

Problem/Motivation

I'm not able to setup 2FA using an authenticator app, getting as result Invalid TOTP code. My setup is already being served under a valid SSL domain.

After having a look to bitwarden_rs issues I found this ones: dani-garcia/vaultwarden#466

And I think that's my issue: the docker container that homeassistant spins up does not have the proper timezone and thus my 2FA attempts fail.

Some commands in order to explain this better:

$ date                               
Sun 10 Nov 2019 09:41:36 PM CET                                    
$ sudo docker exec -it homeassistant date                                                                 
Sun Nov 10 21:43:24 CET 2019                                       
$ sudo docker exec -it addon_a0d7b954_bitwarden date
Sun Nov 10 20:44:13 UTC 2019  

HA's date and bitwardens are set to different TZ (HA has the correct TZ, which matches the first one from the host)

Expected behavior

2FA to work

Actual behavior

Invalid TOTP code error

Steps to reproduce

Just try to enable 2FA from a different TZ than UTC

Proposed changes

This plugin should honor HA's TZ when spinning up the container for Bitwarden

There is a know issue:
got error message "Preflight respons is not succesful" when login with the safari extension.

and it is been fixed in the Bitwarden_rs release 2c2276c

but this bug still represents in this add-on

Can you please update to the latest Bitwarden_rs release to fix it ?

Thanks.

Problem/Motivation

I cannot send emails from Bitwarden as these params are unavailable in the addon

Expected behavior

Have a verification email be sent from Bitwarden when changing email for example

Actual behavior

No email sent, email is not configured for the Bitwarden server

Steps to reproduce

Try changing email in settings

Proposed changes

Open up server to json config form for main params

Problem/Motivation

I have Bitwarden installed on my Home Assistant but suddenly (i don't know if was a update on android version ou HA on the addon-bitwarden ) he stops working on all my android Devices.
The first time e use it, it work perfectly but when i used again, he crash or simply disappear from the screen.
I have the log and i uploaded a movie with the error.
LOGS: https://del.dog/waytonecul.txt
Movie: https://youtu.be/KJDp-aHDxLs

Problem/Motivation

Cannot delete items from Mac Desktop app

Expected behavior

Being able to delete the item

Actual behavior

Can't delete, only works via browser

(Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/605.1.15 (KHTML, like Gecko)) [2020-06-16 17:36:47][request][INFO] PUT /api/ciphers/XXXXXXXXXX/delete [2020-06-16 17:36:47][response][INFO] 404 Not Found [16/Jun/2020:17:36:47 +0200] 404 -(192.168.1.1) PUT /api/ciphers/XXXXXXXXXXX/delete HTTP/1.1

Steps to reproduce

Open the Desktop app, login, try to delete an item

Proposed changes

A fix? Not sure if there is any way I could help debugging this

Problem/Motivation

Cannot open Attachments

Expected behavior

Open Attachments

Actual behavior

An error when I try from iOS App and continuous loading from website

Steps to reproduce

Upload an attachment and try to open it. I try with identities and with login but i have the same issue. I try with PDF and also with images. I try to upload the file from web and also from iOS but i have the same issue.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

When trying to unlock the vault using the APP in linux (tested ubuntu and mint), it fails saying invalid master password. Unlocking using firefox extension works. The workaround is log off and then login again

Proposed changes

This is a known bug, and is already fixed with dani-garcia/vaultwarden#1084

Can you please push this fix to the addon?

Thanks in advance.

Regards

Problem/Motivation

inavlid master password error

Expected behavior

i can login successfully to my self hosted bitwarden vault - but when i lock the application and try to unlock it again the following message is prompted:

"An error has occurred - invalid master password"

Actual behavior

I believe its because my server needs to be updated to 1.63. Its currently 1.14

Hi There,

Is it possible to add this option?

globalSettings__mail__smtp__trustServer=true

So it will not check? I have add a problem also long time ago that Bitwarden cant send emails because of a not valid version ssl problem

Problem/Motivation

Can't open attachments. Have an error

Expected behavior

Open attachments, download file

Actual behavior

In desktop app spinning icon. Can see an error in Developer Console

Steps to reproduce

Create a new item (or use an old one with an attachment). Attempt to open attachment. Open Developer Console and you'll see when opening or editing an item it references https://[url of bitwarden server]:7272/ .... instead when trying to open attachments its: https://localhost/attachments/... which is incorrect. Have attached images of both here:

Proposed changes

bitwarden/server#264 implies this is an issue with the ./bwdata/env/global.override.env file. Correct the entries here.

Problem/Motivation

I'm unable to add U2F authentication to my account.

Expected behavior

I should be able to add FIDO U2F Security Key to my account.

Actual behavior

Getting an error:

DOMAIN environment variable is not set. U2F disabled

Steps to reproduce

Go to "Settings" -> "Two Factor Authentication", select "FIDO U2F Security Key".

Proposed changes

As per Bitwarden_rs documentation, add an option to set DOMAIN environment variable.

I tested Bitwarden with account in cloud and it works from Web app, Chrome extension, Windows app and Android app.
I install Bitwarden addon in Hassio but I can logon only from Web-UI and Chrome extension. It is not possible logon from Windows or Android app. As URL I used IP of RPI https://192.168.1.14:7277

Error says "There is problem connecting to the server" or "Failed to fetch"
In the log appears:

[2019-11-22 11:04:26][rustls::msgs::handshake][WARN] Illegal SNI hostname received [49, 57, 50, 46, 49, 54, 56, 46, 49, 46, 49, 52]

Problem/Motivation

try to export addon-bitwarden to the public, that makes me able to sync all my device cross internet. I also plan to use SNI to secure it. only allow me (knows its the hostname) to access it. I try to use addon NGINX SSL proxy it with the default 443 port. but meet some other trouble with Nginx addon public multiple domains. I will continue try
I try not expose bitwarden 7277 port to the internet directly, instead only expose standard 443 via Assistant addon duckdns and Nginx

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

How to make Bitwarden addon in hassio webui like http:///addon_bitwarden or http:///a0xxxxx_bitwarden/ instead right now http://:7277/

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Since the last update of the addon there are issue with unlocking bitwarden_rs in the browser

Expected behavior

Logging in without issue

Actual behavior

Error: Invalid master password

Steps to reproduce

Just try to unlock the plugin in the browser, enter your correct password and watch the error

Proposed changes

Update the bitwarden_rs addon at leas to version 1.16.2 -> https://github.com/dani-garcia/bitwarden_rs/releases/tag/1.16.2
This issue is fixed in that release: Fixed issue unlocking vault in the desktop client.

If I add a attachment to a personal note or ID, upload is fine, but if i want to download it elsewhere it does not work. On other platforms people had trouble with it, seems like you need to add your domain to env?
bitwarden/server#264
https://community.synology.com/enu/forum/15/post/125219?reply=401226

Thanks guys!

Synology Community

Hi! Come and join us at Synology Community. A place to answer all your Synology questions. Ask a question or start a discussion now.

Hi,

Is there a way to force the admin token or recover it ?
I didn't save it correctly on first startup and it disappeared from the logs very quickly
. I tried portainer but it doesn't seem to want to work on my pi2 (it can't connect to /var/run/docker.sock and I couldn't find anything useful about it online) so I don't see any way of reading the config file in data.

Thank you

My bitwarden wasn't working after upgrading to the latest from 0.116. I"m running the Supervisor version, so I tried to manually pull homeassistant/armv7-addon-bitwarden but it's not available.

Problem/Motivation

Bitwarden refuses to start after update from 0.3.1 to 0.3.2

Expected behavior

Expected a clean update and for it to run again.

Actual behavior

Won't start, results in errors (see below).

Logs

19-11-01 18:51:58 INFO (SyncWorker_18) [hassio.docker.interface] Pull image hassioaddons/bitwarden-aarch64 tag 0.3.2.
19-11-01 18:52:13 INFO (SyncWorker_5) [hassio.docker.interface] Update image sabeechen/hassio-google-drive-backup-aarch64:0.98.4 to sabeechen/hassio-google-drive-backup-aarch64:0.99.0
19-11-01 18:52:13 INFO (SyncWorker_5) [hassio.docker.interface] Pull image sabeechen/hassio-google-drive-backup-aarch64 tag 0.99.0.
19-11-01 18:52:18 INFO (SyncWorker_4) [hassio.docker.interface] Update image esphome/esphome-hassio-aarch64:1.13.6 to esphome/esphome-hassio-aarch64:1.14.0
19-11-01 18:52:18 INFO (SyncWorker_4) [hassio.docker.interface] Pull image esphome/esphome-hassio-aarch64 tag 1.14.0.
19-11-01 18:54:02 INFO (SyncWorker_18) [hassio.docker.interface] Stop addon_a0d7b954_bitwarden application
19-11-01 18:54:11 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-11-01 18:54:41 INFO (SyncWorker_18) [hassio.docker.interface] Clean addon_a0d7b954_bitwarden application
19-11-01 18:54:41 WARNING (SyncWorker_10) [hassio.docker.interface] Can't grep logs from hassioaddons/bitwarden-aarch64: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-11-01 18:54:42 WARNING (SyncWorker_11) [hassio.docker.interface] Can't grep logs from hassioaddons/bitwarden-aarch64: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-11-01 18:54:44 WARNING (SyncWorker_3) [hassio.docker.interface] Can't grep logs from hassioaddons/bitwarden-aarch64: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-11-01 18:54:46 WARNING (SyncWorker_8) [hassio.docker.interface] Can't grep logs from hassioaddons/bitwarden-aarch64: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-11-01 18:54:48 WARNING (SyncWorker_12) [hassio.docker.interface] Can't grep logs from hassioaddons/bitwarden-aarch64: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-11-01 18:54:50 WARNING (SyncWorker_9) [hassio.docker.interface] Can't grep logs from hassioaddons/bitwarden-aarch64: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-11-01 18:54:52 WARNING (SyncWorker_15) [hassio.docker.interface] Can't grep logs from hassioaddons/bitwarden-aarch64: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-11-01 18:54:54 WARNING (SyncWorker_2) [hassio.docker.interface] Can't grep logs from hassioaddons/bitwarden-aarch64: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-11-01 18:54:57 INFO (SyncWorker_5) [hassio.docker.interface] Stop addon_cebe7a76_hassio_google_drive_backup application
19-11-01 18:55:21 INFO (SyncWorker_5) [hassio.docker.interface] Clean addon_cebe7a76_hassio_google_drive_backup application
19-11-01 18:55:22 WARNING (SyncWorker_6) [hassio.docker.interface] Can't find hassioaddons/bitwarden-aarch64 for cleanup
19-11-01 18:55:23 INFO (MainThread) [hassio.addons] Add-on 'a0d7b954_bitwarden' successfully updated
19-11-01 18:55:27 INFO (SyncWorker_3) [hassio.docker.interface] Cleanup images: ['sabeechen/hassio-google-drive-backup-aarch64:0.98.4']
19-11-01 18:55:44 ERROR (SyncWorker_12) [hassio.docker] Can't start addon_a0d7b954_bitwarden: 403 Client Error: Forbidden ("endpoint with name addon_a0d7b954_bitwarden already exists in network hassio")
19-11-01 18:55:44 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<AddonManager.update() done, defined at /usr/src/hassio/hassio/addons/__init__.py:177> exception=AddonsError()>
Traceback (most recent call last):
  File "/usr/src/hassio/hassio/addons/__init__.py", line 217, in update
    await addon.start()
  File "/usr/src/hassio/hassio/addons/addon.py", line 484, in start
    raise AddonsError() from None
hassio.exceptions.AddonsError
19-11-01 18:55:53 INFO (MainThread) [hassio.addons] Add-on 'cebe7a76_hassio_google_drive_backup' successfully updated
19-11-01 18:56:31 INFO (SyncWorker_10) [hassio.docker.addon] Start Docker add-on sabeechen/hassio-google-drive-backup-aarch64 with version 0.99.0
19-11-01 18:56:42 INFO (MainThread) [hassio.api.security] /homeassistant/info access from cebe7a76_hassio_google_drive_backup
19-11-01 18:56:42 INFO (MainThread) [hassio.api.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
19-11-01 18:56:43 INFO (MainThread) [hassio.api.security] /snapshots access from cebe7a76_hassio_google_drive_backup
19-11-01 18:56:43 INFO (MainThread) [hassio.api.security] /snapshots/00499c7e/info access from cebe7a76_hassio_google_drive_backup
19-11-01 18:56:43 INFO (MainThread) [hassio.api.security] /snapshots/af74f702/info access from cebe7a76_hassio_google_drive_backup
19-11-01 18:56:43 INFO (MainThread) [hassio.api.security] /snapshots/a2e45e3e/info access from cebe7a76_hassio_google_drive_backup
19-11-01 18:56:43 INFO (MainThread) [hassio.api.security] /snapshots/711268b7/info access from cebe7a76_hassio_google_drive_backup
19-11-01 19:00:17 INFO (SyncWorker_14) [hassio.docker.interface] Cleanup images: ['esphome/esphome-hassio-aarch64:1.13.6', 'esphome/esphome-hassio-aarch64:latest']
19-11-01 19:00:26 INFO (MainThread) [hassio.addons] Add-on '15ef4d2f_esphome' successfully updated
19-11-01 19:10:16 INFO (SyncWorker_17) [hassio.docker.interface] Clean addon_a0d7b954_bitwarden application
19-11-01 19:10:22 ERROR (SyncWorker_17) [hassio.docker] Can't start addon_a0d7b954_bitwarden: 403 Client Error: Forbidden ("endpoint with name addon_a0d7b954_bitwarden already exists in network hassio")
19-11-01 19:10:35 INFO (SyncWorker_1) [hassio.docker.interface] Clean addon_a0d7b954_bitwarden application
19-11-01 19:10:41 ERROR (SyncWorker_1) [hassio.docker] Can't start addon_a0d7b954_bitwarden: 403 Client Error: Forbidden ("endpoint with name addon_a0d7b954_bitwarden already exists in network hassio")
19-11-01 19:10:41 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<Addon.start() done, defined at /usr/src/hassio/hassio/addons/addon.py:463> exception=AddonsError()>
Traceback (most recent call last):
  File "/usr/src/hassio/hassio/addons/addon.py", line 484, in start
    raise AddonsError() from None
hassio.exceptions.AddonsError
19-11-01 19:11:02 INFO (SyncWorker_11) [hassio.docker.interface] Clean addon_a0d7b954_bitwarden application
19-11-01 19:11:09 ERROR (SyncWorker_11) [hassio.docker] Can't start addon_a0d7b954_bitwarden: 403 Client Error: Forbidden ("endpoint with name addon_a0d7b954_bitwarden already exists in network hassio")
19-11-01 19:13:25 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-11-01 19:14:20 INFO (SyncWorker_10) [hassio.docker.interface] Clean addon_a0d7b954_bitwarden application
19-11-01 19:14:27 ERROR (SyncWorker_10) [hassio.docker] Can't start addon_a0d7b954_bitwarden: 403 Client Error: Forbidden ("endpoint with name addon_a0d7b954_bitwarden already exists in network hassio")
19-11-01 19:16:09 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json```

Problem/Motivation

When I add all the mailserver information. Try to invite a person I get a error in de mailserver log:

ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number

Mailserver is configured to use TLS:

TLS parameters

smtpd_tls_cert_file = /etc/postfix/smtpd.cert
smtpd_tls_key_file = /etc/postfix/smtpd.key
smtpd_use_tls = yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

smtp_tls_security_level = may
smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3
smtpd_tls_protocols = !SSLv2,!SSLv3
smtp_tls_protocols = !SSLv2,!SSLv3

Everything what I try in config of Bitwarden its not sending emails.

It's not the mailserver because all other normal mails will receive and send.

Problem/Motivation

I've lost track of the admin token and I need to be able to administer my local instance.

Expected behavior

I'd like to be able to reset the admin token.

Actual behavior

There is no way to reset the token password. I cannot access the docker in my hassio installation. Not even Portainer sees the running instance. It only sees the container image, not the running container itself.

Steps to reproduce

Install HASSIO in a VM, then install the Bitwarden addon and then restart everything without saving the admin token somewhere.

Proposed changes

Add parameter to either temporarily disable or reset the admin token.

Problem/Motivation

It'd be nice to use TLS v1.3, since this is for a "security product" and TLS v1.3 is the only TLS version that doesn't yet have known vulnerabilities.

Expected behavior

Client negotiates TLS 1.3

Actual behavior

Client negotiates TLS 1.2

Steps to reproduce

Config should enable SSL, setting certificate and key. Then check with curl, e.g.
curl -v --tlsv1.3

I just wanted to ask if you tag versions on some sort of schedule - it seems the code is updated to the newest version of bitwardenrs, but there hasn't been a new release tagged for a while.

Problem/Motivation

I noticed that there is a way to disable user registration with bitwared_rs by using the environment variable : SIGNUPS_ALLOWED=false - i cannot seem to find if I can put that somewhere

Expected behavior

N/A

Actual behavior

N/A

Steps to reproduce

N/A

Proposed changes

Offer a way to disable user registration.

This is just a question.

When a HomeAssistant snapshot is created... the bitwarden data (passwords) is included in the snapshot? If it is not the case, how can the bitwarden data be backed up?

Problem/Motivation

Is it possible that fail2ban or something similar will be implemented to prevent brute force attacks? Bitwarden RS recommend to implement it: https://github.com/dani-garcia/bitwarden_rs/wiki/Fail2Ban-Setup

Currently no ip address will be banned

Expected behavior

Ban ip-address, if there are to much wrong login attempts

Actual behavior

Brute force is possible, no ip address will be banned

Steps to reproduce

Type in the wrong password a lot of times.

Proposed changes

Implement fail2ban or something else to prevent brute force attacks

Problem/Motivation

When i create a new entry with an URL it crash and the console say that it is tryng to get favicon

Expected behavior

I expect that the addon get the image and show it.

Actual behavior

The addon crash for 2/3m.

Steps to reproduce

Add an entry with an URL

The "configs\hassio\addons\data\a0d7b954_bitwarden\config.json" file contains plain text account login data, such as the Admin token for Bitwarden and the SMTP username & password.

This presents a security risk (albeit a small one, if your server's file system is properly secured).

Encrypting this data would be more secure, and is therefore preferable - especially when dealing with a password storage database.

Problem/Motivation/Question:

Hello,

I have a question about the releases (apart from that I am super satisfied with the app), but I see that it is already 7 versions behind ... is that correct?

is there any way to update this?
I am on version 2.13.2, and see that 2.17.1 is out.

Problem/Motivation

The Bitwarden Android app complains with an error message when attempting to login. As a result it is unable to login to Bitwarden running as a Hassio app.

(Why the issue was filed)

Expected behavior

The App should be able to login

(What you expected to happen)

Actual behavior

An error has occurred
Exception message: Handshake failed

(What actually happened)

Steps to reproduce

Install the Let's Encrypt app and generate a certificate using a Full Qualified Domain Name

Configure Bitwarden to use the new fqdn and HTTPS protocol with Let's Encrypt cert

Point the app to the FQDN using: https://fqdn:7277

(How can someone else make/see it happen)

Proposed changes

I am not sure where the problem lies specifically but as Hassio uses a reverse Nginx proxy to proxy the secure ssl information to apps behind it, it seems like a possible cause.
Currently TLSv1.2 and TLSv1.3 is enabled by default in the proxy config. I attempted to add TLSv1.0 and TLSv1.1 but with no success.

I wonder if it has something to do with the ssl ciphers?

I have checked the certificate in addition using many different tools and everything looks good, browsers also do not complain either so the certificates seem to be fine.

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

When removing/adding entry on the web Vault, everything because super laggy, and unresponsive.
I have had the page completely freeze with a white screen, the only way to access the page again was to refresh it, which cancels out the current actions.

Expected behaviour

Be responsive, without any hangs or performance issues.

Actual behaviour

The page becomes unresponsive, and freezes.

Steps to reproduce

Mass delete/edit any item on the web Vault.

Proposed changes

The issue had originally been raised on the bitwarden_rs repo, but it was found to be an issue with the hass add-on instead.
See here: dani-garcia/vaultwarden#1453

Problem/Motivation

Chrome extension locks. Unlocking is not possible with master password (error occured). Logging out and logging in works though with exactly the same password. Apparantly updating docker fixes the problem: https://www.reddit.com/r/Bitwarden/comments/jzs1hx/cant_unlock_my_vault_but_can_logout_and_back_in/

Expected behavior

Unlock

Actual behavior

Doesn't unlock and message appears: error occured.

Steps to reproduce

Let extension lock and try to unlock.

Proposed changes

Update docker to latest version?

I did see my admin token when I first started the addon but I cant see it anymore (after editing some settings).
When I restart I have this:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Bitwarden RS
 Open source password management solution
-----------------------------------------------------------
 Add-on version: 0.6.2
 You are running the latest version of this add-on.
 System: HassOS 4.15  (amd64 / qemux86-64)
 Home Assistant Core: 0.116.4
 Home Assistant Supervisor: 2020.10.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[09:50:07] INFO: Starting the Bitwarden RS server...
/--------------------------------------------------------------------\
|                       Starting Bitwarden_RS                        |
|                           Version 1.14.2                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Report URL: https://github.com/dani-garcia/bitwarden_rs/issues/new |
\--------------------------------------------------------------------/
[2020-10-28 09:50:07][start][INFO] Rocket has launched from http://0.0.0.0:80
[2020-10-28 09:50:07][ws][INFO] Listening for new connections on 0.0.0.0:8080.
[09:50:07] INFO: Starting NGinx...

Any idea how to access it again ?

Problem/Motivation

I'm trying to invite new users and also adding users to my orginisation. Both function require a mail to be sent.
So i've configured a smtp server (which is operational), but I can't test the integration.

Expected behavior

I expect the bitwarden application to sent a mail to the email address entered.

Actual behavior

No mail is sent (nothing seen in the smpt server) and the interface returns an Unknown Error.
It does note the mail address as invited.
In the log it says the following when inviting a user:

[2019-08-16 22:00:54][rocket::rocket][INFO] POST /admin/invite/ application/json:
[2019-08-16 22:00:54][_][INFO] Matched: POST /admin/invite (invite_user)
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Custom { kind: Other, error: StringError("failed to lookup address information: Temporary failure in name resolution") })', src/libcore/result.rs:999:5

And when (re-)inviting a user to the organisation:

[2019-08-16 22:10:00][_][INFO] Matched: POST /api/organizations/<org_id>/users/<user_org>/reinvite (reinvite_user)
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Custom { kind: Other, error: StringError("failed to lookup address information: Temporary failure in name resolution") })', src/libcore/result.rs:999:5

So same error. Some name resolution thing. When it is strange that other application (my mail server itself, can sent mails via the same smtp

Steps to reproduce

Adding a smtp server configuration the bitwarden vault and then inviting a user.

Impossible to logon and can't validate "create an account" from chrome or vivaldi, when you click on the unlock button there is an error message :

An error has occurred.
Cannot read property 'importKey' of null

If you create an account with chrome you will see this error message and after the password is not correctly set.

Works perfectly with edge.
The bug does not exist on the official bitwarden website (with the same version number : 2.10.1 )