Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Could not open database error #278

Open
5 tasks done
Maddiehn22 opened this issue Feb 2, 2024 · 5 comments
Open
5 tasks done

[BUG]: Could not open database error #278

Maddiehn22 opened this issue Feb 2, 2024 · 5 comments
Labels

Comments

@Maddiehn22
Copy link

⚠️ This issue respects the following points: ⚠️

  • This is a single bug, not a question or a configuration/webserver/proxy issue.
  • This is not a bug in the Nextcloud App or another client.
  • This issue is not already reported on Github (I've searched it).
  • Nextcloud Server and the Passwords App is up to date. See Nextcloud Apps.
  • The browser extension is up to date. See Nextcloud Apps.

Server Information

No acces to cli

Client Information

Browser and Version:115.7.0 est
Client OS and Version: WIN7
Extension Version: 2.6 & 2.5

Bug description

Extension reports : Could not open database

Steps to reproduce

Open a password protected website
No password and usser will be inserted

Expected behavior

No automatic password insert works
No search works

Extension Logs

Error log from FF extension:
{"details":{"data":{"event":{"isTrusted":true}},"message":"Could not open database","file":"moz-extension://17469bde-5a99-4bef-8b77-246e6b54f101/js/background.js","line":2,"stack":"7588/load/e.onerror@moz-extension://17469bde-5a99-4bef-8b77-246e6b54f101/js/background.js:2:827708\n","time":1706807661652},"error":{"name":"Error","stack":["7588/load/e.onerror@moz-extension://17469bde-5a99-4bef-8b77-246e6b54f101/js/background.js:2:827708",""],"string":"Error: Could not open database","fileName":"moz-extension://17469bde-5a99-4bef-8b77-246e6b54f101/js/background.js","lineNumber":2,"columnNumber":827708,"message":"Could not open database"}}


GET /index.php/apps/dashboard/
from 80.128.242.138 by admin at 2024-02-02T09:43:40+00:00
{"reqId":"RNEi5DhMfMXcVYkttbTk","level":3,"time":"2024-02-02T09:22:10+00:00","remoteAddr":"80.128.242.138","user":"User","app":"no app in context","method":"GET","url":"/index.php/apps/dashboard/","message":"Dashboard widget passwords-widget took 2.9 seconds to load.","userAgent":"Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0","version":"26.0.10.1","data":[],"id":"65bcb97cbae54"}
@Maddiehn22 Maddiehn22 added the bug label Feb 2, 2024
@Maddiehn22
Copy link
Author

@marius-wieschollek
Copy link
Owner

What browser is this?
Are you using any specific settings that could impact the extensions ability to use the IndexedDB browser functionality?

@Maddiehn22
Copy link
Author

Maddiehn22 commented Feb 2, 2024 via email

marius-wieschollek added a commit that referenced this issue Mar 27, 2024
Signed-off-by: Marius David Wieschollek <passwords.public@mdns.eu>
@marius-wieschollek
Copy link
Owner

In the telegram channel, a user reported that the extension will not work if the "always browse in private mode" setting is enabled. This could also happen if the "create history" settings is set to never.

I have added a workaround to the nightly release that will just fall back to an in-memory database if it's unable to use the browser database feature.
In that case you will now see the warning "Persistent database not available. Maybe always private browsing is enabled?" in the extension logs. And suggested passwords will not be as good as there is no recommendation data.

@Maddiehn22
Copy link
Author

Maddiehn22 commented Mar 27, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants