Open Be-Mann opened 3 weeks ago
Just wanted to add that I'm seeing this as well on Brave browser (which uses Chrome extensions).
Sounds like an extension issue to me so i'm moving this
Yeah, it is becoming almost unusable. I am getting the same error and must log in every time I use the extension.
TLDR: Chrome reboots the extension every 30 seconds to be "more efficient".
So there seem to be a few errors mixed up here. The Error 429 - i have no clue currently where it comes from. I guess it's a side effect from the main issue. The "Could not establish connection" is a common error when tabs/popups or anything is closed while the extension communicates with them.
Here is how i understand what happens: Chrome "suspends" Manifest V3 extensions when not active. This seems to be done by just stopping the "service worker" and then starting it back up when needed. It seems that any context is not restored.
For the passwords extension that is a bit of an issue since the service worker (formerly the background page in Manifest V2) is where it keeps the local copy of the password database and the session with the Nextcloud server. Periodic events do not prevent Chrome from stopping and restarting the service worker. So tasks like the session keepalive check every minute don't help.
So simply put, the extension seems to be rebooted every 30 seconds which logs you out and also clears all local data, including the error log and local passwords.
My experience with Manifest V3 is limited, but looking online i found this stackoverflow answer archive which lists some workarounds for this genius new behavior.
I will release a nightly update soon with a workaround implemented and update this ticket.
The development build with the update is released, would be great if you could give feedback if it works for you.
Hi Marius I have been using it for an hour, and it looks better. There has been no logout so far. I will let you know if any issues come up.
Appreciate your work. Jack
I concur, I've been using it all morning, and it's perfect. Thank you @marius-wieschollek!
⚠️ This issue respects the following points: ⚠️
Server Information
Client Information
Browser and Version: Chrome 130.0.0.0 Client OS and Version: Windows 10 Pro 64bit, Version 19045.5073
Bug description
Recently I have been frequently logged out of the Password Manager extension (on both servers), sometimes immediately after logging in and sometimes only after 30 seconds or so. I am connected to two servers, one of which is connected via VPN.
The extension log shows "Too Many Requests" as an error message. Addendum: And it sometimes shows "Error: Could not establish connection" to one server.
But basically I am always logged out of both instead of just one.
Steps to reproduce
Open the Password Manager Chrome Extension. Log in to the account. Perform any action (e.g., access a stored password). After a short while (sometimes immediately), I am logged out, and the message "Too Many Requests" or "Error: Could not establish connection" appears in the log.
Expected behavior
I should stay logged in to the extension after logging in, without unexpected logout due to "Too many requests" or "Could not connect", (especially if it's only on a short timeout (1-2 seconds by vpn) and the connection is back afterwards.
Nextcloud Logs
Browser Logs
Addendum to the log: