Vaultwarden does not connect in client #4

Open
opened 2026-08-30 15:48:46 +02:00 by tdpeuter · 0 comments
Owner

The Vaultwarden server is outdated to the point that new recent clients are unable to connect to it.

Current server version: vaultwarden/server:1.35.4-alpine
Latest version: vaultwarden/server:1.37.2-alpine

Breaking changes/upgrade path: Doesn't seem to be any. Upgrade incrementally I would say. 1.35 -> 1.36 -> 1.37 -> 1.37.2

I think I just want to apply these version fixes locally, as I don't want to go through the hassle of fixing the flow again. On the other hand, there is also the backup issue that the ssh keys are out of sync.

The Vaultwarden server is outdated to the point that new recent clients are unable to connect to it. **Current server version:** vaultwarden/server:1.35.4-alpine **Latest version:** [vaultwarden/server:1.37.2-alpine](https://hub.docker.com/layers/vaultwarden/server/1.37.2-alpine/images/sha256-2e635df29ecd942515f79d26932b879a723764981376572cac2cc2bb5e7604bc) **Breaking changes/upgrade path:** Doesn't seem to be any. Upgrade incrementally I would say. 1.35 -> 1.36 -> 1.37 -> 1.37.2 I think I just want to apply these version fixes locally, as I don't want to go through the hassle of fixing the flow again. On the other hand, there is also the backup issue that the ssh keys are out of sync.
tdpeuter added the
bug
label 2026-08-30 15:48:46 +02:00
tdpeuter self-assigned this 2026-08-30 15:48:46 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Bos55/nix-config#4
No description provided.