Unable to use Bitwarden CLI in code-server terminal

[exodar]

When I execute the Bitwarden CLI from a code-server terminal, it immediately returns a prompt with no output whatsoever. You can't even access --help. However, if I SSH into the same box that code-server is running on with the same user that code-server is running as, I can execute it just fine.

I'm using the latest Bitwarden CLI from here:

https://vault.bitwarden.com/download/?app=cli&platform=linux

[im-coder-lg]

Firstly - do you use HTTPS? A lot of these issues are related to WebView. Does Bitwarden really work locally v/s your code-server web env?

[exodar]

No I'm using HTTP to access my code-server. Bitwarden does indeed work from an SSH terminal outside of VS Code, but nothing when using the code-server terminal. This can be reproduced by downloading the Bitwarden CLI and just running 'bw --help'.

It's very strange.

[im-coder-lg]

I sus WebView. Can you try enabling HTTPS on your instance?

[jsjoeio]

However, if I SSH into the same box that code-server is running on with the same user that code-server is running as, I can execute it just fine.

I can also do this (running code-server on my macOS locally).

I don't know why it wouldn't work on a remote machine though 🤔

Can you run code-server --log trace and then try using bw again? I wonder if we'll get anything in the server logs. Or even the browser logs.

[exodar]

Nothing appeared in trace log. Also attached output of me running it directly in SSH session.

[jsjoeio]

This is very very odd. I do see "profile not validated". Is there a different shell profile you can try?

[exodar]

I'm using ZSH, but I've tried .bashrc and .profile as well as switching to /bin/bash. Same results. Assuming that's what you mean.

…

On Mar 1, 2022, at 10:45 AM, Joe Previte ***@***.***> wrote: This is very very odd. I do see "profile not validated". Is there a different shell profile you can try? — Reply to this email directly, view it on GitHub <#4922 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQQ3LKQDMMUW2G27BACZETU5Y3TFANCNFSM5PRD5YJQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.

[jsjoeio]

[im-coder-lg]

Woah @jsjoeio are you ok? I have never seen you posting screenshots like that! Everything good?

[jsjoeio]

LOL yes, don't worry. I made that in Preview on macOS 🤣 The replies in GitHub Discussions are confusing so hoping to make it more clear.

[code-asher]

Weird, I get the same issue. I spun up code-server 4.1.0 and tried:

$ wget -O bw.zip 'https://vault.bitwarden.com/download/?app=cli&platform=linux'
$ unzip bw.zip
$ chmod +x bw
$ ./bw --help

[code-asher]

In my case this works:

NODE_OPTIONS= ./bw --help

It does not seem to like when NODE_OPTIONS is set.

We should remove this anyway: #2878

But still not sure why this causes this issue.

[exodar]

Im hoping to try out HTTPS later this week when I have more time to configure it to see if that helps. If it does help, I'm using Ubuntu Server 20.04 on an Intel platform for my code-server implementation. There's nothing else installed on the box, it's super bare-bones.

…

On Mar 1, 2022, at 1:25 PM, Joe Previte ***@***.***> wrote: LOL yes, don't worry. I made that in Preview on macOS 🤣 The replies in GitHub Discussions are confusing so hoping to make it more clear. — Reply to this email directly, view it on GitHub <#4922 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQQ3LICR3CYRCN7I7QJ3STU5ZOKJANCNFSM5PRD5YJQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.

[jsjoeio]

Okay let us know how that goes. 🤞

[exodar]

I’ll try this and report back. Thanks, Rob Emenaker ***@***.***

…

On Mar 8, 2022, at 5:45 PM, Asher ***@***.***> wrote:  In my case this works: NODE_OPTIONS= ./bw --help It does not seem to like when NODE_OPTIONS is set. We should remove this anyway: #2878 But still not sure why this causes this issue. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.

[exodar]

This works!

…

On Mar 8, 2022, at 5:45 PM, Asher ***@***.***> wrote: In my case this works: NODE_OPTIONS= ./bw --help It does not seem to like when NODE_OPTIONS is set. We should remove this anyway: #2878 <#2878> But still not sure why this causes this issue. — Reply to this email directly, view it on GitHub <#4922 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQQ3LK5FSQMMCHTELIYGVTU67KBZANCNFSM5PRD5YJQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.

[jsjoeio]

Solution posted by @code-asher

In my case this works:

NODE_OPTIONS= ./bw --help

It does not seem to like when NODE_OPTIONS is set.

We should remove this anyway: #2878

But still not sure why this causes this issue.