Bitwarden node, does it support self-hosted Vaultwarden?

[DanielH]

I am trying the Bitwarden node.
Thwere is an option (Environment) for “Self-Hosted” when entering the Client-ID and Client Secret to the Bitwarden account setting.
Could it be that only the Self-Hosted Bitwarden server is supported, but not Vaultwarden?

What is the error message (if any)?

Error code

400

Full message

{ “error”: “”, “errorModel”: { “message”: “Malformed client_id”, “object”: “error” }, “error_description”: “”, “exceptionMessage”: null, “exceptionStackTrace”: null, “innerExceptionMessage”: null, “message”: “Malformed client_id”, “object”: “error”, “validationErrors”: { “”: [ “Malformed client_id” ] } }

Please share your workflow

Share the output returned by the last node

Bad request - please check your parameters
Malformed client_id

Information on your n8n setup

• n8n version: 1.107.4
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker

[Zelite]

@DanielH The “Self-Hosted” option in the Bitwarden node probably means it works with the official Bitwarden server you set up yourself, and it might not work with Vaultwarden, which is a different version. Try putting in your Client ID, Client Secret, and server URL to test it with Vaultwarden, but if it doesn’t work, it might only support the official Bitwarden.

[codersaur]

Did you ever find a solution to this? I am trying to use the Bitwarden node to connect to my self-hosted vaultwarden instance and getting the same error.