RE: https://infosec.exchange/@masek/116579264376811608

I switched to Keepass a few months ago not because of reliability issues with Bitwarden itself but out of fear a cloud-based password manager would be taken over just like that.

if you're still using Bitwarden, switch over while you can.

@e12 I personally host my own Vaultwarden instance. You can use it with any Bitwarden client, you have all of the paywalled features, and all the data is stored in your server.
I really recommend it to anyone that has the possibility to self-host it. If not, Keepass is a great alternative :)

https://github.com/dani-garcia/vaultwarden

GitHub - dani-garcia/vaultwarden: Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs

Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs - dani-garcia/vaultwarden

GitHub
@malasaur I did try to host it on my personal machine with Podman a few days ago and ran into a lot of trouble setting it up. Maybe I could try to host it once more I dunno
@e12 my philosophy specially in selfhosting is to never drop an idea just because I run into issues. That's what selfhosting's all about. Our instance is proof of that.
What issues did you run into? I could give you a hand if you want

@malasaur the issue I have is relating to setting write permissions for rsa_key.pem key, maybe relating to me trying to run it rootless. Just finished investigating once again while trying out different quadlet configs but to no avail

EDIT: I actually gave up and created a volume instead of a home directory for it lol. it worked, I guess?

@e12 EDIT: my bad, I just read your edit lol
Yeah, great that you solved it yourself lol

yeah, I'm not really a fan of Podman anymore 😅
Try setting write permissions to its folder, I recall it being something like

$ podman run --rm it vaultwarden/server id
# Get Vaultwarden's UID and GID
$ podman chown UID:GID /path/to/vaultwarden/data

That should do the trick (hopefully)

@malasaur now the prominent issue I have is obtaining https certs for my vaultwarden because somehow it requires https now. how'd you go around and do it? and how I might do it without a domain?
@e12 I use Caddy to proxy Vaultwarden's port 80 directly, works amazingly. Caddy should be able to proxy without a domain. Have Podman forward Vaultwarden's port 80 to something internal, and then have Caddy proxy that port to some other one over HTTPS, without any domain
@malasaur I'll try to investigate once again with this way
@e12 Aye, best of luck to you :)