[GH-ISSUE #4029] Unable to login into CLI #1753

New issue

Closed

opened 2026-03-03 02:11:48 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:11:48 +03:00

Owner

Originally created by @pthoelken on GitHub (Nov 5, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4029

Steps To Reproduce

Download the latest CLI Linux Binary
Mount it into your container image (/usr/bin/bw)
Run bw login --apikey (also tried with --raw) and put in the exact chars from https://yourdomain.vault.local/#/settings/security/security-keys
Become the error message below (also tried with the whitespace from "client_id" from the website.

root@75481d729f41:/# bw login --apikey --raw
? client_id: user.XXXXXXXXXXXX
? client_secret: XXXXXXXXXXXXXXXXXXXXX
client_id or client_secret is incorrect. Try again.

Expected Result

Successfull login

Actual Result

root@75481d729f41:/# bw login --apikey --raw
? client_id: user.XXXXXXXXXXXX
? client_secret: XXXXXXXXXXXXXXXXXXXXX
client_id or client_secret is incorrect. Try again.

Screenshots or Videos

Additional Context

No response

Operating System

Linux

Operating System Version

Container - Latest Image

Shell

Bash

Build Version

2023.10.0

Issue Tracking Info

I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Originally created by @pthoelken on GitHub (Nov 5, 2023). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/4029 ### Steps To Reproduce 1. Download the latest CLI Linux Binary 2. Mount it into your container image (/usr/bin/bw) 3. Run `bw login --apikey` (also tried with --raw) and put in the exact chars from https://yourdomain.vault.local/#/settings/security/security-keys 4. Become the error message below (also tried with the whitespace from "client_id" from the website. ``` root@75481d729f41:/# bw login --apikey --raw ? client_id: user.XXXXXXXXXXXX ? client_secret: XXXXXXXXXXXXXXXXXXXXX client_id or client_secret is incorrect. Try again. ``` ### Expected Result Successfull login ### Actual Result ``` root@75481d729f41:/# bw login --apikey --raw ? client_id: user.XXXXXXXXXXXX ? client_secret: XXXXXXXXXXXXXXXXXXXXX client_id or client_secret is incorrect. Try again. ``` ### Screenshots or Videos ![image](https://github.com/bitwarden/clients/assets/12643853/277a86d3-71ac-4f3c-8e4c-f620e6501f58) ![image](https://github.com/bitwarden/clients/assets/12643853/eb9bb359-a454-4a8a-b8cd-3f0b80263d85) ### Additional Context _No response_ ### Operating System Linux ### Operating System Version Container - Latest Image ### Shell Bash ### Build Version 2023.10.0 ### Issue Tracking Info - [X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

kerem closed this issue

2026-03-03 02:11:48 +03:00

kerem commented

2026-03-03 02:11:49 +03:00

Author

Owner

@pthoelken commented on GitHub (Nov 5, 2023):

Howly cow ...

bw config server https://yourvault.local.com
I'm so sorry. Solved.

@pthoelken commented on GitHub (Nov 5, 2023): Howly cow ... `bw config server https://yourvault.local.com ` I'm so sorry. Solved.