BitWarden IPv6 bug (& workaround) 

Apparently Bitwarden's Android client has a bug in scenarios where both the client device and the server have routeable IPv6 addresses (

Hacky workaround: I added a second DNS entry (vault4.domain) that only has an IPv4 address, added it to the nginx vhost config and added it to the LetsEncrypt TLS cert.

Configuring the Android client with the IPv4-only hostname seems to make it happy.

(In theory you could do the same with just the IPv4 address but that makes the situation un-ideal for a good, valid TLS cert)

Sign in to participate in the conversation

Mania Systems a retro-futurist themed community for independent, underground, and non-traditional artists and creatives who want to share their work, meet each other, and collaborate, all in a safe space. We specifically try to build for the intersections of being queer, being chronically ill or disabled, being neuroatypical, and being mixed-race or brown - because that's who we are.