search

bitwarden / clients

Bitwarden client apps (web, browser extension, desktop, and cli).
https://bitwarden.com
Other
9.31k stars 1.26k forks source link

Websocket cockpit pending when bitwarden enable #6817

Open vuducmanh11 opened 1 year ago

vuducmanh11 commented 1 year ago

Steps To Reproduce

  1. Go to cockpit webserver
  2. Click on 'Login' after bitwarden autofill user and password
  3. Scroll down cockpit sidebar and click to 'Terminal' tab

Expected Result

Cockpit terminal display properly

Actual Result

White screen shell, websocket pending

Screenshots or Videos

Additional Context

I'm using cockpit for accessing ssh from web

Operating System

Linux

Operating System Version

CentOS 7

Web Browser

Chrome

Browser Version

Version 119.0.6045.105 (Official Build) (64-bit)

Build Version

2023.10.1

Issue Tracking Info

NovaSilentium commented 1 year ago

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

vuducmanh11 commented 1 year ago

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

Certainly, I will provide an update if I discover any further information

mmcphee commented 1 year ago

Ran into this issue today. When Bitwarden extension is enabled on the browser, and I refresh cockpit, it won't load. When it is disabled, and I refresh the page again, it will load. CockpitError

ratavaz commented 1 year ago

Hi, I'm having the same issue as [vuducmanh11] with just some minor differences. In my instance at times after the login I have the same white screen as shown in [vuducmanh11] pictures while other times the screen is completely white, without even the left hand side menu. When the screen is fully white and I try to reload the page I end up back to the Cockpit login page.

I'm running Cockpit on a Raspberry PI 3 OS is Raspberry PI OS based on Debian 11 (Bullseye)

I can systematically reproduce the problem with:

Bitwarden Estension version is 2023.10.2

Cockpit is reachable through reverse proxy with ngnix but the same issue is present even if I directly access Cockpit without passing through nginx.

Some additional information:

  1. If I use Bitwarden extension to add login and password to the Cockpit login page, then disable the extension before logging in, everything works. If I re-enable the extension at that point everything keeps working, even in case of page reload or logoff and new login. It seems that something messes up Cockpit login procedure but once the login has been completed that specific step is not repeated on subsequent logins.
  2. My Cockpit configuration allows me to jump from the server on which Cockpit interface is installed to another server allowing me to control both from the same interface. When I can manage to have Cockpit showing the left hand side menu, if I jump to the second server everything works perfectly with it but the main server keeps giving the white page as to [vuducmanh11].
  3. In my instance everything has worked for a while then suddenly stopped, cannot trace back if due to an update to the Bitwarden Extension or to the browser, due to the timing it seems more probable that the trigger was the extension update, but cannot say it for sure.

The only error I can find in the log (journalctl -u cockpit) is the following:

Any help you could provide is welcome

Best Regards Paolo

Newspring-ple commented 12 months ago

Explain what happens

Description: I am experiencing an issue with Cockpit when the Bitwarden extension is enabled. After signing in, the page loads to a white screen. This issue occurs consistently across all my Cockpit sessions on different servers. When I disable the Bitwarden extension, Cockpit loads as expected. However, when I enable the Bitwarden extension after Cockpit has loaded, only the left menu bar is available, and the rest of the screen remains white.

Steps to Reproduce:

  1. Enable the Bitwarden extension in the browser.
  2. Log in to Cockpit.
  3. Observe that the page loads to a white screen.
  4. Disable Bitwarden extension, refresh Cockpit, and observe normal behavior.

Browser Information:

Additional Information:

Workaround: To access Cockpit with the Bitwarden extension enabled, I have been using a private window in Firefox and pasting passwords from the regular Bitwarden extension.

Additional Notes: I have tested this issue on both Firefox and Chrome, and the problem persists.

Expected Behavior: Cockpit should load normally with the Bitwarden extension enabled.

Thank you for your assistance in resolving this issue.

Version of Cockpit

Version 250.1.1.

rivman commented 11 months ago

I have the same issue, Firefox 120.0 (64 bits) and Bit Warden 2023.10.2 White page on Cockpit dashboard after login. Manually entered credentials or not :

Uncaught ReferenceError: cockpit is not defined

When disabling the FF Extension, page works. Already put domain in exceptions and all is not blocked in Firefox. Thanks.

vuducmanh11 commented 10 months ago

Today, this bug seems fixed

ratavaz commented 10 months ago

Today, this bug seems fixed

Sadly not for me, I'm still experiencing the bug on Edge, Chrome and Firefox updated to the latest available version via the browsers auto-update and using the latest available Bitwarden extension (Version 2023.12.1), at least according to the browser extension stores.

@vuducmanh11: Could you please let me know which browser and which version of the Bitwarden extension have you tested?

Thanks Paolo

Newspring-ple commented 10 months ago

Sorry, I still am having the same issue also, I am willing to share a zoom session and show you what it looks like on my end.

[image: image.png]

[image: image.png]

On Mon, Jan 8, 2024 at 4:24 AM ratavaz @.***> wrote:

Today, this bug seems fixed

Sadly not for me, I'm still experiencing the bug on Edge, Chrome and Firefox updated to the latest available version via the browsers auto-update and using the latest available Bitwarden extension (Version 2023.12.1), at least according to the browser extension stores.

@vuducmanh11 https://github.com/vuducmanh11: Could you please let me know which browser and which version of the Bitwarden extension have you tested?

Thanks Paolo

— Reply to this email directly, view it on GitHub https://github.com/bitwarden/clients/issues/6817#issuecomment-1880729965, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS6XG3MODCYME3TT5YBCYCLYNPCN5AVCNFSM6AAAAAA7AVX6BSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQG4ZDSOJWGU . You are receiving this because you commented.Message ID: @.***>

Newspring-ple commented 10 months ago

Also does not work on [image: image.png] [image: image.png]

On Tue, Jan 9, 2024 at 4:06 PM Patrick Emerson < @.***> wrote:

Sorry, I still am having the same issue also, I am willing to share a zoom session and show you what it looks like on my end.

[image: image.png]

[image: image.png]

On Mon, Jan 8, 2024 at 4:24 AM ratavaz @.***> wrote:

Today, this bug seems fixed

Sadly not for me, I'm still experiencing the bug on Edge, Chrome and Firefox updated to the latest available version via the browsers auto-update and using the latest available Bitwarden extension (Version 2023.12.1), at least according to the browser extension stores.

@vuducmanh11 https://github.com/vuducmanh11: Could you please let me know which browser and which version of the Bitwarden extension have you tested?

Thanks Paolo

— Reply to this email directly, view it on GitHub https://github.com/bitwarden/clients/issues/6817#issuecomment-1880729965, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS6XG3MODCYME3TT5YBCYCLYNPCN5AVCNFSM6AAAAAA7AVX6BSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQG4ZDSOJWGU . You are receiving this because you commented.Message ID: @.***>

Newspring-ple commented 10 months ago

[image: image.png] Has same issue, Sorry for the 3 emails, I just thought I better be thorough, Thanks for your help on this. Let me know if there is any way I can help.

On Tue, Jan 9, 2024 at 4:09 PM Patrick Emerson < @.***> wrote:

Also does not work on [image: image.png] [image: image.png]

On Tue, Jan 9, 2024 at 4:06 PM Patrick Emerson < @.***> wrote:

Sorry, I still am having the same issue also, I am willing to share a zoom session and show you what it looks like on my end.

[image: image.png]

[image: image.png]

On Mon, Jan 8, 2024 at 4:24 AM ratavaz @.***> wrote:

Today, this bug seems fixed

Sadly not for me, I'm still experiencing the bug on Edge, Chrome and Firefox updated to the latest available version via the browsers auto-update and using the latest available Bitwarden extension (Version 2023.12.1), at least according to the browser extension stores.

@vuducmanh11 https://github.com/vuducmanh11: Could you please let me know which browser and which version of the Bitwarden extension have you tested?

Thanks Paolo

— Reply to this email directly, view it on GitHub https://github.com/bitwarden/clients/issues/6817#issuecomment-1880729965, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS6XG3MODCYME3TT5YBCYCLYNPCN5AVCNFSM6AAAAAA7AVX6BSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQG4ZDSOJWGU . You are receiving this because you commented.Message ID: @.***>