I found this comment on what happened by dani-garcia, one of the main devs:

The short version is that around 8-ish years ago, Bitwarden changed the way the vault items were structured, and Vaultwarden added some backwards compatibility fields to ensure both old and new versions of the clients worked.

These backwards compatibility fields were supposed to be a temporary measure, but for at least the next three years the clients still required them, until we eventually forgot to keep track of them. At some point between 2021 and today, the clients stopped requiring these backwards compatibility fields, but Vaultwarden was still sending them.

This wasn’t a problem until Bitwarden decided to use the backwards compatibility fields in a completely different way, which caused the clients to crash.

Found here: https://github.com/dani-garcia/vaultwarden/discussions/7473

I like these posts, I feel like there are many levels to any self hosted setup and getting an idea of what everyone is doing is fun.

I did it, well… because I could.

That is a very valid reason. I could see setting it up to learn more about how IPv6 works. I just wanted to see if I could get any actual advantages with it.

office situation where there are a large number of devices

That would make sense as a place to have it. Having a large number of devices where each having an external IP would be handy. My environment really only needs one or two devices having direct external access.

I mean, I don’t have NAT traversal between my NAS and devices on my lan now, they are routed because they are different VLANs but that would happen anyway.

Do people have problem with ip conflicts? I guess if I wasn’t running DHCP that would be possible.

Right now NAT is my main firewall between most devices and the wider internet, but I do still run pfsense and have firewall rules in place.

Switching over to IPv6 seems like it would be extra work for very little actual benefit.

What do you get out of IPv6 for lan routing vs just sticking to IPv4 for everything?