search

alex3305 / home-assistant-addons

Alex's Home Assistant Add-ons
https://alex3305.github.io/home-assistant-docs/
MIT License
47 stars 29 forks source link

Default Bitwarden server is not working anymore #37

Closed ElVit closed 2 years ago

ElVit commented 2 years ago

Hello @alex3305,

since some time my Bitwarden-Secrets-Addon does not working anymore. I use the default server in my configuration:

server: 'http://a0d7b954-bitwarden'

If I change the server to 

server: http://Home-Assistant-IP:Bitwarden-Port

then it's working again. Can you tell my maybe why the default address doesn't work anymore?

alex3305 commented 2 years ago

Hi @ElVit,

Thanks for this feedback. I had noticed this too and thought it was because of my own configuration. Which I changed up quite a lot 🤷. It seems that I needed to add the Bitwarden port to get it working again:

server: http://a0d7b954-bitwarden:7277/
username: homeassistant@localhost.lan
password: homeassistant
organization: Home Assistant

I think this is because of some change to the Vaultwarden add-on, but I'm not 100% sure about this. Can you verify that this is also working for you? Than I can change this in the default configuration and documentation.

ElVit commented 2 years ago

You are right, thanks. It's working again 😃. The strange thing is that in my BitWarden addon configuration I changed the port, but with this link it has to be the default port 7277. Maybe it's worth to mention it in your addon docs.

chpego commented 2 years ago

Maybe using this bashio function to get option of BitWarden addon (if it's installed)

alex3305 commented 2 years ago

@ElVit I have just amended the docs and default config in 93f6ac22e34fea42dac3debf9065190cdf5f9ce8.

@chpego I think it is possible to do, but why should I? The hostname of the add-on doesn't change anyway and thus adds complexity. And of course something that could break in the future. I'm going to stick with the current solution. But I appreciate your feedback ❤️!