-
Subject of the issueI get an error "Wrong username or password" when trying to log in with the browser extension. Deployment environment
Steps to reproduceI'm using the following values: vaultwarden:
image:
repository: vaultwarden/server
tag: testing
pullPolicy: IfNotPresent
env:
SIGNUPS_ALLOWED: false
INVITATIONS_ALLOWED: true
DOMAIN: https://vault.example.com
SMTP_HOST: example.com
SMTP_FROM: no-reply@example.com
WEB_VAULT_ENABLED: true
ADMIN_TOKEN: "< TOKEN >"
ingress:
enabled: true
annotations:
kubernetes.io/ingress.class: traefik
kubernetes.io/tls-acme: "false"
traefik.ingress.kubernetes.io/router.entrypoints: websecure
traefik.ingress.kubernetes.io/router.tls: "true"
path: /
hosts:
- vault.example.com
tls:
- secretName: vaultwarden-example-cert
hosts:
- vault.example.com
pathType: Prefix
persistence:
enabled: false
accessMode: ReadWriteOnce
size: 3200Mi
storageClass: longhorn-replicated
#existingClaim: "bitwarden-pvc"Expected behaviourI can log in with the web extension. Actual behaviourI tried it on Firefox and Chromium, it happens on multiple devices. I can log into the web vault and on Android apps. My account is set up with an authenticator app and FIDO2. The web browser extension version is 2023.1.0 Troubleshooting dataIn server logs: There are no relevant logs in Traefik. This is a fresh install, not a migration from a previous version. I tried it on a fresh browser, so it doesn't seem to be cache. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Are you sure you configured the correct host for the browser extension via the gear icon? |
Beta Was this translation helpful? Give feedback.
-
|
I just found the issue, the host was correct. Somehow this was caused by the lack of a persistent volume. I don't know how the web UI still worked fine, but something specifically about browser extensions caused it to fail without a persistent volume, even though the container never restarted and would still work on mobile / web during all this. Just adding back the persistent volume (I had set persistence to false for testing) fixed it.. |
Beta Was this translation helpful? Give feedback.
I just found the issue, the host was correct.
Somehow this was caused by the lack of a persistent volume. I don't know how the web UI still worked fine, but something specifically about browser extensions caused it to fail without a persistent volume, even though the container never restarted and would still work on mobile / web during all this. Just adding back the persistent volume (I had set persistence to false for testing) fixed it..