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.
{
"details": {
"data": {
"_response": {},
"_status": 429
},
"message": "HTTP 429 - Too Many Requests",
"stack": [
"TooManyRequestsError: HTTP 429 - Too Many Requests",
" at f.getClass (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:558803)",
" at _.getClass (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:622342)",
" at O._getHttpError (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:575959)",
" at O.send (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:573668)",
" at async n.getFavicon (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:608824)",
" at async chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:902052"
],
"time": 1730897648057
},
"error": {
"name": "TooManyRequestsError",
"stack": [
"TooManyRequestsError: HTTP 429 - Too Many Requests",
" at f.getClass (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:558803)",
" at _.getClass (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:622342)",
" at O._getHttpError (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:575959)",
" at O.send (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:573668)",
" at async n.getFavicon (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:608824)",
" at async chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:902052"
],
"string": "TooManyRequestsError: HTTP 429 - Too Many Requests",
"message": "HTTP 429 - Too Many Requests",
"_response": {},
"_status": 429
}
}
Addendum to the log:
{
"details": {
"data": {
"id": "9a1f302a-f360-4704-8b8c-ac449cdcbc14",
"tab": null,
"type": "queue.items",
"reply": null,
"silent": false,
"sender": "background",
"channel": "runtime",
"payload": {
"name": "authorisation",
"items": [
{
"id": "a0ceda2f-f32d-482c-8633-11bca268efb1",
"task": {
"server": "370c693e-3559-4695-b9b5-d399dd97b199",
"label": "XXXXXX xxxx@xxxxxx.de",
"password": true,
"token": false,
"providers": []
},
"result": {},
"success": null,
"accepted": false,
"feedback": {}
}
]
},
"receiver": null
},
"message": "Could not establish connection. Receiving end does not exist.",
"stack": "Error: Could not establish connection. Receiving end does not exist.\n at h (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:776309)",
"time": 1730920307930
},
"error": {
"name": "Error",
"stack": [
"Error: Could not establish connection. Receiving end does not exist.",
" at h (chrome-extension://mhajlicjhgoofheldnmollgbgjheenbi/js/background.js:2:776309)"
],
"string": "Error: Could not establish connection. Receiving end does not exist.",
"message": "Could not establish connection. Receiving end does not exist."
}
}
⚠️ 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: