Vaultwarden API 500: Internal Server Error #1430

New Issue

OVERLORD · 2026-02-05T00:55:25+03:00

OVERLORD commented

2026-02-05 00:55:25 +03:00

Originally created by @modarken on GitHub (Dec 15, 2022).

Subject of the issue

Using Postman to try and connect to vaultwarden API I get a 500: Internal Server Error

Deployment environment

Docker

vaultwarden version: 1.26
Install method:
docker pull
Clients used:
chrome
Other relevant details:

Steps to reproduce

POST /public/identity/connect/token HTTP/1.1
Host: bitwarden.test.local
Content-Type: application/x-www-form-urlencoded
Content-Length: 136

grant_type=client_credentials&scope=api&client_id=user.xxxxx&client_secret=6Yxxxxx

Expected behavior

json return of token

Actual behaviour

500: Internal Server Error

The server encountered an internal error while processing this request.

Rocket

</html>

Troubleshooting data

Originally created by @modarken on GitHub (Dec 15, 2022). ### Subject of the issue Using Postman to try and connect to vaultwarden API I get a 500: Internal Server Error ### Deployment environment Docker * vaultwarden version: 1.26 * Install method: * docker pull * * Clients used: * chrome * Other relevant details: ### Steps to reproduce POST /public/identity/connect/token HTTP/1.1 Host: bitwarden.test.local Content-Type: application/x-www-form-urlencoded Content-Length: 136 grant_type=client_credentials&scope=api&client_id=user.xxxxx&client_secret=6Yxxxxx ### Expected behavior json return of token ### Actual behaviour <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>500 Internal Server Error</title> </head> <body align="center"> <div role="main" align="center"> <h1>500: Internal Server Error</h1> <p>The server encountered an internal error while processing this request.</p> <hr /> </div> <div role="contentinfo" align="center"> <small>Rocket</small> </div> </body> </html> ### Troubleshooting data

OVERLORD added the enhancement label 2026-02-05 00:55:25 +03:00

OVERLORD closed this issue

2026-02-05 00:55:29 +03:00

OVERLORD commented

2026-02-05 00:55:32 +03:00

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

Vaultwarden doesn't support the Bitwarden Public API, so that will never work.
At this moment Vaultwarden only supports the client API, which is why your request fails.

If you really want to login this way, make sure to use the client API, which also provides a device_identifier and device_name
The device_identifier is a v4 UUID, which stays unique per device/client and keeps the same per user, even if it is the exact same device/application.

@BlackDex commented on GitHub (Dec 15, 2022): Vaultwarden doesn't support the Bitwarden Public API, so that will never work. At this moment Vaultwarden only supports the client API, which is why your request fails. If you really want to login this way, make sure to use the client API, which also provides a `device_identifier` and `device_name` The `device_identifier` is a v4 UUID, which stays unique per device/client and keeps the same per user, even if it is the exact same device/application.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1430