mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-07-17 09:22:30 -05:00
[GH-ISSUE #7292] Registration fails with "missing field key" #30161
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MatthiasKuehneEllerhold on GitHub (Jun 3, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7292
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: ADMIN_TOKEN
Failed HTTP Checks:
Config:
Vaultwarden Build Version
1.36.0-1+1.1, webvault: 2026.4.1-1+1.1
Deployment method
OS Package (apt, yum/dnf, pacman, apk, nix, ...)
Custom deployment method
No response
Reverse Proxy
2.4.67-1~deb12u2
Host/Server Operating System
Linux
Operating System Version
Debian 12
Clients
Desktop
Client Version
2026.5.0
Steps To Reproduce
Using the web GUI works though!
Expected Result
Registration via the App works.
Actual Result
Registration errors out.
Logs
Screenshots or Videos
No response
Additional Context
No response
@stefan0xC commented on GitHub (Jun 3, 2026):
Yes, that is currently impossible. As explained in the wiki this can happen when there is a breaking change made by Bitwarden, since we don't control the clients (and can only make sure the web-vault is compatible). So until we implement the new API, Vaultwarden is currently not compatible with clients with version
2026.5.0(or later). Cf. https://github.com/dani-garcia/bw_web_builds/pull/245@GuilhermeNobre commented on GitHub (Jun 4, 2026):
This error apply to extensions? I'm trying connect to extensions on Google Chrome or chromium and is not working
@stefan0xC commented on GitHub (Jun 4, 2026):
It applies to everything that uses the new registration API. I don't want to come across as rude but this bug report is specifically about registration and likely has nothing to do with connecting an extension (as far as I've tested it that still works without issue). Since the issue tracker is not meant as a support forum I want to ask that you open a separate thread in discussions and provide more details like the support string from the Vaultwarden admin panel.