Ну Санкции и т д. Да и вообще стоит ли доверять свои чувствительные данные этому сервису? А что если завтра в миг прекратит свое существование сервис? Что будет с данными? Bitwarden мне нравится но боюсь .

I'm trying to deploy Vaultwarden in my k3s cluster, and it's mostly working...except the service and ingress. The app is running, but it is totally inaccessible. I'm not sure whether I need to use my DeSEC subdomain or whether I can use a .internal fake domain and access it over VPN.

This is the relevant part of my code:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: vaultwarden
  namespace: vaultwarden
  labels:
    app: vaultwarden
spec:
  replicas: 1
  selector:
    matchLabels:
      app: vaultwarden
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: vaultwarden
    spec:
      restartPolicy: Always
      containers:
        - name: vaultwarden
          image: vaultwarden/server:latest
          env:
            - name: DOMAIN
              value: http://vaultwarden.mafmanhomelab.dedyn.io
          ports:
            - containerPort: 80
              protocol: TCP
          volumeMounts:
            - mountPath: /data
              name: vaultwarden-claim0
      volumes:
        - name: vaultwarden-claim0
          persistentVolumeClaim:
            claimName: vaultwarden-claim0


apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: vaultwarden
  namespace: vaultwarden
  labels:
    app: vaultwarden
spec:
  rules:
    - host: "vaultwarden.mafmanhomelab.dedyn.io"
      http:
        paths:
          - path: "/"
            pathType: Prefix
            backend:
              service:
                name: vaultwarden
                port:
                  number: 8000

apiVersion: v1
kind: Service
metadata:
  name: vaultwarden
  namespace: vaultwarden
  labels:
    app: vaultwarden
spec:
  selector:
    app: vaultwarden
  ports:
  - name: "http"
    port: 8000
    targetPort: 8000

Hey everyone,

I'm running into a sync issue with the latest Bitwarden clients and my self-hosted Vaultwarden instance and wanted to check if anyone else is experiencing this.

The Situation:

• Web-Vault works fine: Accessing the vault directly via the web interface works without any issues.
• Works on other devices: The sync continues to work completely fine on my Android phone and on other PCs.
• Fails on Linux Mint: After updating to Bitwarden Desktop / Browser Extension v2026.7.0 on my Linux Mint machine, the sync fails completely.

When launching the Desktop App from the terminal, I caught an unhandled error pointing to a type mismatch: Unhandled error in angular Error: Error: invalid type: JsValue(Object({"fido2Credentials":[], ...})), expected a string

What I've Already Tried:

I already attempted to fix this by modifying the array to a string in the export/data structure, but that didn't resolve the issue. Given that everything works smoothly on other devices and the Web-Vault, I suspect the underlying cause might actually be something else entirely rather than just the vault data itself.

Has anyone encountered this specific sync failure with version 2026.7.0, and what potential causes or solutions are there?

why Vaultwarden not have thier app ?

because I want app for it to update app and system in same time not I waiting until fix for bitwarden app compatibility

copy paste bitwarden app but after fixing bug publish Bitwarden app update in Vaultwarden app

of course Bitwarden extension fork needed in same

My vault is shown as empty on every form of the Bitwarden app except on the website. I entered the correct self-hosted URL because it logs me in to my account without a problem ( the account has all the correct personal info ) but the vault is empty. About my setup : I self host vault warden in a Proxmox LXC (i used the helper script). On top of the base Vaultwarden install i use fail2ban. The local IP is exposed to the public using a Cloudflare tunnel. Any help is appreciated !

EDIT : yeah i just needed to update Vaultwarden . Thanks for the help :3

Is this normal? I see the same for many other processes and this is a single user self hosted instance.

https://preview.redd.it/x3zlvwdnoxih1.png?width=1756&format=png&auto=webp&s=e4047df5a5cdd2b4482a5e1e4ec9a0f74dd4e740

Hey everyone,

I'm self-hosting Vaultwarden on a VPS and using cloudflared (Cloudflare Tunnel) for DNS and routing. To secure the instance, I set up a Cloudflare Access policy that requires users to belong to a specific domain and verify their identity via a PIN sent to their email.

This setup is applied widely to the entire domain, including subdomains and the problem is that this authentication layer completely blocks the browser extension from communicating with the server.

How are you guys handling this? Is there a way to bypass the Zero Trust authentication specifically for the API/extension calls without leaving the instance and other apps wide open? Any tips or alternative setups would be appreciated

After wanting to self-host for a few years, I finally committed in recent months, and as a previous user of Dashlane and Keeper Security, I knew I wanted a self-hosted password manager. I love how minimalistic Vaultwarden is. I've got it installed as an app on my UGREEN DXP4800 Plus, running TrueNAS / Tailscale.

When I migrated 900+ passwords over, I knew there would be some cleanup needed, so I started going through the web interface / vault. I started at the top of the list and as I went farther down the list, I started seeing duplicates. So for me, the next step is to filter those duplicates so they are the only records in the view. I found it to be a pita to have to scroll all the way to the top of that list to get to the Filters / Search Vault field.

So my request is for the developers to make that section of the page, that Filter box static, just like the main menu to the left of it. Anyone with me on this?

Помогите. Что лучше в плане безопасности и надёжности ( чтобы в дальнейшем не потерять данные).

Help. What is better in terms of security and reliability ( to avoid losing data further).