extensions
extensions copied to clipboard
[Bitwarden] load failed: error:04800066:PEM routines::bad end line
Extension
https://www.raycast.com/jomifepe/bitwarden
Raycast Version
1.78.1
macOS Version
15.0 Beta Version(24A5279h)
Description
I have set the Clinet ID and the Client Secret, when I input my master password, it always tell me my master password were not right.
and these are log
Warning: Ignoring extra certs from `/Users/xxxx/.config/raycast/ca.pem`, load failed: error:04800066:PEM routines::bad end line
Invalid master password.
Steps To Reproduce
- install extensions
- set Clinet ID and Client secret
- input master password
Current Behaviour
Warning: Ignoring extra certs from `/Users/xxxx/.config/raycast/ca.pem`, load failed: error:04800066:PEM routines::bad end line
Invalid master password.
Expected Behaviour
Just please let me login.
Thank you for opening this issue!
🔔 @jomifepe @daniel-stoneuk @andreaselia @pernielsentikaer @eth-p @YamenSharaf @undefinedzack @anirudhganwal06 @ivaarsson you might want to have a look.
💡 Author and Contributors commands
The author and contributors of jomifepe/bitwarden can trigger bot actions by commenting:
@raycastbot close this issueCloses the issue.@raycastbot rename this issue to "Awesome new title"Renames the issue.@raycastbot reopen this issueReopens the issue.@raycastbot assign meAssigns yourself to the issue.@raycastbot good first issueAdds the "Good first issue" label to the issue.@raycastbot keep this issue openMake sure the issue won't go stale and will be kept open by the bot.
I make sure the master password is right, and I have login with bw in the terminal.
I'd like to add that I have the same issue, while I'm using macOS 14.5 (23F79) and Raycast 1.78.1, so that's not macOS beta issue.
I am sure the master password is entered correctly. In my case however, I'm not using bitwarden-cli installed via Homebrew, but I download the bw binary myself and put it to /usr/local/bin/bw. The path is properly configured in the extension's config.
@jomifepe need help please
Hey, can you make sure you don't have any leading or trailing spaces in your client id and secret? The extension simply looks for an Invalid master password response from the CLI, so something must be wrong. The other error that's above the message looks completely unrelated with the extension and it's probably not causing the issue.
UPDATE 2: Version 2024.7.2 was release and according to the changelog, it addresses this issue directly. ~UPDATE 1: Version 2024.7.1 was released, be sure to try that one also if you're on 2024.6.1.~
It's likely that the issue is on the CLI's side (related issue), please try downgrading to 2024.6.0, I stopped being able to unlock after logging in with client and secret on 2024.6.1. Downgrading with homebrew is a bit of a pain, so I suggest npm or downloading it from here (x64 only but works on arm64) and either replacing the bw binary in the installed location (usually /opt/homebrew/bin/bw or /usr/local/bin/bw) or pointing the extension to the downloaded one using the preferences.
Just to confirm: I've downgraded my CLI to 2024.6.0, logged out from it, logged back in, checked if I can unlock my vault and after it worked, tried again in Raycast extension — worked as well. Thanks for your support, @jomifepe! 👍🏻
@allinu Can you confirm if this works for you?
Just want to say I ran into this issue.
https://github.com/bitwarden/clients/issues/9919#issuecomment-2251406604 helped me get to version 2024.6.0.
Now it works
Just want to say I ran into this issue.
bitwarden/clients#9919 (comment) helped me get to version
2024.6.0.Now it works
Hey, awesome that it worked for you, be aware that it's pinning your version, so it won't be updated next time.
Just want to say I ran into this issue. bitwarden/clients#9919 (comment) helped me get to version
2024.6.0. Now it worksHey, awesome that it worked for you, be aware that it's pinning your version, so it won't be updated next time.
Thanks for the heads up! When since I'm following this thread, I'll know when it's fixed and will unpin. Thanks!
@allinu Feel free to comment if the issue persists.
@raycastbot close this issue