I have installed Vaultwarden as Hass OS addon. As I experienced some problems i want to switch the system to an LXC Container. Question is now, how can I access the Data folder of the addon, so I can export it and import it to the Bitwarden LXC Installation?
I managed to find the Data with portainer, but dunno how to save the data anywhere where I can get it.
No idea how to do it with portainer, I don’t use it. If it gives you access to the docker cli, use the command I linked above. If not, can connect a monitor and keyboard and use the host shell. Or use the community ssh addon with protection mode disabled.
Or just extract a backup. The /data directory of the addon should be in there.
I tried to stay local with my installation, so only http approach. If i want to get access from outside, I have a wireguard server running. BUT meanwhile it only works properly -as far as I understand and experienced- with https and ssl certificate. And attachements didn’t work properly either. So I decided to take it to a standalone installation and try to get lucky with this
You can run a vaultwarden as LAN only with a let’s encrypt certificate, they have a guide on how to do it:
The key is you need to be able to use a non-http challenge with certbot. Usually that means buying your own domain so you can use a DNS challenge. Then you don’t actually need to point the domain at your IP and port forward port 80 to prove ownership. Then you can have the domain resolve to a LAN IP (like they show). Or simply run your own DNS server in your LAN and add a DNS rewrite rule so your domain resolves differently in your LAN from everywhere else.
Actually some googling turned up this so you may not even need to buy a domain anymore. Sounds like DuckDNS now supports DNS-01 challenges as an alternative to the HTTP one.
Oh you just wanted to put it behind a reverse proxy instead of adding a cert to it directly? Fair enough. Didn’t want to use nginx proxy manager, caddy or one of the other reverse proxies that have been turned into addons already?
Not in the first place. I want to have a stable local running version which i can access through my vpn. But as its comlpicated and intensive in maintenance i choose now the port forwarded version behind a reverse proxy