Bitwarden Firefox extension keeps logging out

maneesh29s · July 27, 2024, 4:47am

In chrome I have updated the extension to 2024.6.2, still I am facing this logout issue.
My vault timeout action is set to Lock and not log out.
But bitwarden extension does not even remember my email once I go back.

I also tried removing the extensions and installing again, still its not working.

grb · July 27, 2024, 5:01am

This is fixed in version 2024.7.1.

maneesh29s · July 27, 2024, 8:48am

In web store it still shows 2024.6.2 as the latest version.

Hisasasa · July 27, 2024, 10:16am

Firefox 129
Bitwarden 2024.6.3
There’s still a problem.

grb · July 27, 2024, 1:19pm

Chrome app store needs a few days to approve the new release.

grb · July 27, 2024, 1:21pm

See this comment.

fham · August 13, 2024, 6:25pm

Started having a problem with Firefox extension closing Bitwarden earlier today, happened several times as discussed here. After finding this thread, I was checking current versions for my response and noted FF was updating; after updates so far everything seems to working correctly. Win10, FF ver 129.0.1, BW ver 2024.7.1

mattkrins · December 12, 2024, 10:19pm

Still getting this bug on FF 133.0.3, BWV 2024.11.2.
Set to stay logged in, but randomly completely logs out when browser has not even been closed.

Hisasasa · January 8, 2025, 8:23am

This bug hasn’t been fixed in a long time, and it’s infuriating.

Firefox dev edition 134, self-host 2024.12.0, Firefox Addon 2024.12.3

The most annoying thing is that the logout happens on all versions of the Windows Portable client.

github.com/bitwarden/clients

Session out again

opened 05:12PM - 25 Aug 24 UTC

baek-sang

bug browser

### Steps To Reproduce You have a fresh installation of the Firefox extension. … Logout occurred while the browser was still working (2 different PC) ### Expected Result Keeping sessions alive ### Actual Result logout ### Screenshots or Videos _No response_ ### Additional Context https://github.com/bitwarden/clients/issues/8873 ### Operating System Windows ### Operating System Version 11 ### Web Browser Firefox ### Browser Version 130 ### Build Version 2024.7.1 ### 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.

abelgvidal · January 8, 2025, 7:09pm

I am experiencing this bug.

Firefox 133.0.3 (64-bit)
Extension bitwarden v 2024.12.3
OS Linux Mint

It logouts randomly several times a day even not closing browser.

Any help is appreciated.

dmayan · April 8, 2025, 7:31pm

Same problem here, Firefox 137.0, Win11 Pro
Bitwarden Extension Version 2025.2.0

It began happening 1 or 2 weeks ago. Tried reinstalling the extension again to no avail.

Thanks, Diego

hmoffatt · October 23, 2025, 12:31am

This is happening to me every day on one computer only - Firefox extension on Windows, no desktop BitWarden installed, everything up to date. I’ve just uninstalled and reinstalled the extension to see if that helps.

Nail1684 · October 23, 2025, 9:56am

If not, then do it again and make sure that the local data of the browser extension was deleted between deinstall and reinstall.

hmoffatt · October 23, 2025, 11:16pm

It happened again. The data location in Firefox seems to change every time you reinstall the extension (the UUID changes) anyway, and removing the extension seems to be removing the old local data, so there’s nothing else to delete.

So I’m not sure what to do next or how to debug this.

hmoffatt · October 27, 2025, 1:18am

I left the console for the extension open. It’s logged out within 24 hours again. I’m not sure exactly when.

21:04:25.038 [SignalR] Close message received from server. console-log.service.ts:43:17

21:04:25.040
[SignalR] Connection disconnected with error 'Error: Server returned an error on close: Connection closed with an error.'. console-log.service.ts:51:17

09:05:17.655 XHRGET https://api.bitwarden.com/accounts/revision-date
[HTTP/2 401  1430649ms]

09:29:07.552 Firefox can’t establish a connection to the server at wss://notifications.bitwarden.com/hub?access_token=... vendor.js:2:37879

09:29:07.560 [SignalR] (WebSockets transport) There was an error with the transport. console-log.service.ts:43:17

09:29:07.561
[SignalR] Failed to start the connection: Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled. console-log.service.ts:51:17

09:29:09.084 [PhishingDetectionService] No active account. console-log.service.ts:43:17

09:29:09.098 Retrieving application id

Environment did not respond in time, emitting previous config. console-log.service.ts:43:17

09:29:09.902 [PhishingDetectionService] No active account. console-log.service.ts:43:17

09:29:10.086 can't access property "id", e is null console-log.service.ts:47:17

09:29:10.949
GET
wss://notifications.bitwarden.com/hub?access_token=...
[HTTP/1.1 401 Unauthorized 3544ms]

09:29:11.052 can't access property "id", e is null console-log.service.ts:47:17
09:29:11.187 Cannot find menu item with id autofill console-log.service.ts:47:17
09:29:11.374 can't access property "id", e is null console-log.service.ts:47:17
09:29:11.451 Cannot find menu item with id copy-password console-log.service.ts:47:17

09:29:12.098 [PhishingDetectionService] Initialize called. Checking prerequisites... console-log.service.ts:43:17

09:29:12.112 WebAssembly is supported in this environment browser-sdk-load.service.ts:51:13

09:29:12.120 Retrieving application id console-log.service.ts:43:17
09:29:12.182 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    Fx index.ts:116
background.js:1:1035362

09:29:12.279 WASM SDK loaded in 166ms console-log.service.ts:43:17
09:29:12.284 State version: 72

Micah_Edelblut · October 27, 2025, 1:03pm

Hi @hmoffatt, thanks for the helpful console logs!

Looking through them, it’s clear that the 401 response on the API call is what is causing the logout. What’s less clear is why this call is getting that response. It is a very long call (24 minutes) which is quite unusual - are there any issues that might be happening with your network that could cause this?

A couple of questions that might help us debug this:

are you logged into multiple accounts in the extension?
do you have any sort of browser settings, extensions, or system automations that would cause the system storage for your browser to be cleared?

hmoffatt · October 27, 2025, 10:57pm

Thanks for responding @Micah_Edelblut . Looking at the console trace some more, I see that the GET of https://api.bitwarden.com/accounts/revision-date has the following header in the response:

www-authenticate: Bearer error=“invalid_token”, error_description=“The token expired at ‘10/27/2025 19:05:26’”

Same for the GET of wss://notifications.bitwarden.com/hub?access_token=…

I’m only logged into my one personal Bitwarden account.

I don’t have any automatic storage cleaning going on that I’m aware of - I’m staying logged into everything else OK, including this community site. But my other Firefox+Bitwarden installs all work fine so there must be something like that going on.

hmoffatt · October 28, 2025, 7:51am

I’ll add that if I deliberately restart Firefox, the extension stays logged in (but locked) ok.

Micah_Edelblut · October 28, 2025, 12:36pm

Our current theory is that network conditions prevented the call from making it to the server for long enough that the auth token expired between the call being sent and the server receiving it. Is there unique going on with the network this device is connected to that might cause significant delays like this?

hmoffatt · October 29, 2025, 7:40am

The computer sleeps when idle, but so do all my others that work ok (Windows and Linux). I didn’t see any other network errors in the console. Should there be a refresh of the access token before the fetch of the revision-date endpoint that fails?