github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-05-24 09:03:15 -05:00
Code Issues 307 Packages Projects Releases 83 Wiki Activity

[GH-ISSUE #2978] Unable to create new users, api_not_found in logs #14220

New Issue
Closed
opened 2026-04-23 05:58:48 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-23 05:58:48 -05:00
Owner
Copy Link

Originally created by @maurice-audin on GitHub (Dec 13, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2978

Subject of the issue

Cannot create new users, errors api_not_found in logs

Deployment environment

  • Vaultwarden version: v1.26.0
  • Web-vault version: v2022.11.2
  • Running within Docker: false (Base: Debian)
  • Environment settings overridden: false
  • Uses a reverse proxy: true
  • IP Header check: false (X-Forwarded-For)
  • Internet access: true
  • Internet access via a proxy: false
  • DNS Check: true
  • Time Check: true
  • Domain Configuration Check: true
  • HTTPS Check: true
  • Database type: SQLite
  • Database version: 3.35.4
  • Clients used:
  • Reverse proxy and version:
  • Other relevant information:

Steps to reproduce

Build last releases for vaultwarden and web vault from sources

Expected behaviour

User creation

Actual behaviour

Red popup (see screenshot) and this in logs:

[request][INFO] GET /api/devices/knowndevice/[MAIL]/[ID]
[_][WARN] Response was `None`.
[_][WARN] Responding with registered (api_not_found) /api 404 catcher.
[response][INFO] (web_files) GET /<p..> [10] => 404 Not Found

Troubleshooting data

screenshot

Originally created by @maurice-audin on GitHub (Dec 13, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2978 ### Subject of the issue Cannot create new users, errors api_not_found in logs ### Deployment environment * Vaultwarden version: v1.26.0 * Web-vault version: v2022.11.2 * Running within Docker: false (Base: Debian) * Environment settings overridden: false * Uses a reverse proxy: true * IP Header check: false (X-Forwarded-For) * Internet access: true * Internet access via a proxy: false * DNS Check: true * Time Check: true * Domain Configuration Check: true * HTTPS Check: true * Database type: SQLite * Database version: 3.35.4 * Clients used: * Reverse proxy and version: * Other relevant information: ### Steps to reproduce Build last releases for vaultwarden and web vault from sources ### Expected behaviour User creation ### Actual behaviour Red popup (see screenshot) and this in logs: ``` [request][INFO] GET /api/devices/knowndevice/[MAIL]/[ID] [_][WARN] Response was `None`. [_][WARN] Responding with registered (api_not_found) /api 404 catcher. [response][INFO] (web_files) GET /<p..> [10] => 404 Not Found ``` ### Troubleshooting data ![screenshot](https://user-images.githubusercontent.com/851854/207306445-fd8d6a20-01b0-4929-b1ae-29d630860875.png)
GiteaMirror commented 2026-04-23 05:58:50 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Dec 13, 2022):

You are using an incompatible Vaultwarden server.
Please use the testing tagged images which contain the latest and compatible web-vault already instead of merging them your self.

<!-- gh-comment-id:1348333025 --> @BlackDex commented on GitHub (Dec 13, 2022): You are using an incompatible Vaultwarden server. Please use the `testing` tagged images which contain the latest and compatible web-vault already instead of merging them your self.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#14220
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?