In case anyone else comes across this problem, it’s in bitwardenurl/admin, login must take place with the admin token, not the user and pass, the admin token is generated at the beginning of the log in hass.io when starting the addon and should definitely be pasted somewhere else after obtaining it, as saving anything in /admin will make it stop appearing in the hass.io logs in the future.
Indeed, but I didn’t make the connection with the location of the SMTP settings, as they are located there and are actually essential if more than one person intends to use Bitwarden.
Do you mind if I add the SMTP info to your installation instructions on Github?
Only the main UI allows adding users, but the invites never show up unless SMTP is set up in the admin UI, an aspect which I feel is not at all clear
I only ever access my hass.io externally through the Nabu Casa cloud, is there any way to get the BitwardenRS service to work through nabu casa, instead of installing SSL cert?
example: https://.nabu.casa:7277
I have tried to figure out how but cannot get it to work.
That is basically what I do. I use the Nginx Proxy Manager add-on and added 2 proxy hosts. The main domain (DuckDNS) pointing to Home Assistant (port 8123) and a subdomain (DuckDNS also forwards that to my external IP) to the Bitwarden port (7277).
Current setup
I have the DuckDNS addon, with config for LetsEncrypt. DuckDNS forwards my-domain.duckdns.org to my IP. My router forwards 443 to HA (8123) and 7277 to BW (7277)
New setup
I have the DuckDNS addon, but do not use LetsEncrypt with it. DuckDNS forwards my-domain.duckdns.org to my IP. My router forwards 443 to to HA (8123)