The server encountered an internal error while processing this request.
Rocket
</html>
Troubleshooting data
Originally created by @modarken on GitHub (Dec 15, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2990
### 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
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.
<!-- gh-comment-id:1353182632 -->
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @modarken on GitHub (Dec 15, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2990
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
<html lang="en"> <head> </head>500: Internal Server Error
The server encountered an internal error while processing this request.
Troubleshooting data
@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_identifieranddevice_nameThe
device_identifieris a v4 UUID, which stays unique per device/client and keeps the same per user, even if it is the exact same device/application.