Install method: Vaultwarden runs on Azure App Service using the image from docker hub with the tag "vaultwarden/server:latest" and data folder mapped.
Clients used: CLI 2024.6.0 even downgrading wouldn't solve the issue running on Azure app service as a docker without mapping.
Reverse proxy and version: None
MySQL/MariaDB or PostgreSQL version: PostgreSQL 14.11
Other relevant details:
Steps to reproduce
I can't seem to find a proper way to reproduce the issue but last thing I did when it started acting like that was upgrading Bitwarden CLI client from 2024.4.1 to 2024.6.0 I also increased KDF to the recommended size on Vaultwarden user settings.
Subject of the issue
I just started having random auth issues on Bitwarden CLI that runs in a docker on Azure app service and serves an HTTP endpoint.
Deployment environment
Install method: Vaultwarden runs on Azure App Service using the image from docker hub with the tag "vaultwarden/server:latest" and data folder mapped.
Clients used: CLI 2024.6.0 even downgrading wouldn't solve the issue running on Azure app service as a docker without mapping.
Reverse proxy and version: None
MySQL/MariaDB or PostgreSQL version: PostgreSQL 14.11
Other relevant details:
Steps to reproduce
I can't seem to find a proper way to reproduce the issue but last thing I did when it started acting like that was upgrading Bitwarden CLI client from 2024.4.1 to 2024.6.0 I also increased KDF to the recommended size on Vaultwarden user settings.
Expected behaviour
Bitwarden CLI will lock the vault only.
Actual behaviour
Bitwarden CLI is losing the authentication.
Troubleshooting data
Bitwarden CLI becomes unauthenticated returning:
On Vaultwarden Logs i have:
Bitwarden CLI Dockerfile:
entrypoint.sh
I tried to remove the rsa* files and they regenerated but the issue still persists until i restarted the CLI docker.
Any hint?
Thank you!