jhass
Nextcloud-keeweb no longer accepting my password even though it is correct
Like the title says. Running most recent version of Nextcloud on a Raspberry Pi, all apps up to date. When I access it from a web browser I open the database file in Keeweb and type in my password. It gets rejected. No caps lock. I even typed it into notepad in Windows and copy/pasted it, didn't work; typed it into gedit in Fedora and copy/pasted it, didn't work. Tried it in Firefox, Chrome, and Ungoogled Chromium in both Windows and Fedora. I rebooted the Pi, no change. I uninstalled Keeweb and reinstalled it, no change. I uninstalled Keeweb, rebooted the Pi, reinstalled Keeweb, no change.
Nobody else has access to any of this; they would need at least three passwords and my yubikey to be able to change the password themselves (and the password hasn't been changed as noted in the title).
It's not the end of the world bc it still works on Keepass2Android and KeepassX in Windows and Fedora, but being able to access it on any computer around the world and just copy/paste passwords is a huge convenience bonus for me so I don't have to go through my layers of security on my phone to get to Keepass2Android and sit there and look at the password and then slowly type it out because all of them are 30 characters long or more with a ton of letters, numbers, and special characters.
Is this a bug with the Keeweb app in Nextcloud? A bug in Nextcloud itself? Anybody else ever experience this? Should I just reinstall Nextcloud? Not a big deal if that's what I have to do, but I would like to try something less drastic before that.
Thank you all in advance for any advice or help you can offer.
Sorry, I can not reproduce this here. It works just fine as usual with Firefox, Edge, Chrome and Vivaldi.
Can you please check in the web developer console if there are any error messages when you try to open the database file (usually F12 and then the "Console" tab of the developer tools).
Edit: did you try to create a new database file using a simple password like "test123" just to see if it works with other files?
HI, The same issue for me : Unable to open a file with keeweb. It is possible with the windows app. No log in nextcloud. Maybe a keeweb issue : this is the same probrem with https://app.keeweb.info/
Mmmmm... After changing the master key with the windows app, I am now able to open the file :/
Hi, sorry for being late to the show. I can confirm the same behaviour here, which occurred all of a sudden. The only possible "change" to a setup that worked for years was a recent upgrade to NC 27 or 27.0.2 - but honestly, I'm not using keeweb on a regular basis so the actual root cause can have occured weeks or months (?) ago without being related to NC upgrades.
Anyway: I checked devtools on Chrome for what happens when entering the password. Note: I clicked on my kdbx file from inside the "files" app of NextCloud and the password input appears. Upon submitting my password, there's an HTTP 403 for accessing the kdbx file.
For privacy reasons (we're talking about my keepass file here after all, right?) I'll replace sensitive parts of the information from the console log by "folder", "file" and "servername.tld":
2023-08-14T09:38:07.125Z [app] Loaded app config from config?file=%2FFOLDER%2FFILE.kdbx 336ms
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:07.130Z [settings-manager] Theme changed light
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:07.224Z [start-profiler] App started in 3067ms: fetching=700ms, pre-init=2426ms, loading modules=137ms, document ready=56ms, creating app model=5ms, loading configs=1ms, initializing modules=2ms, loading remote config=347ms, checking features=1ms, initializing storage=0ms, starting usb=0ms, first view rendering=93ms, app ready event=0ms
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:07.741Z [browser-extension-connector] Started
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:35.460Z [open:/folder/file.kdbx on SERVERNAME.TLD] File open request
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:35.461Z [open:/folder/file.kdbx on SERVERNAME.TLD] Open file from storage webdav
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:35.461Z [open:/folder/file.kdbx on SERVERNAME.TLD] Load from storage
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:35.462Z [storage-webdav] Load https://SERVERNAME.TLD/remote.php/webdav/folder/file.kdbx?requesttoken=averylongtokenhere
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1
GET https://SERVERNAME.TLD/remote.php/webdav/folder/file.kdbx?requesttoken=averylongtokenhere 403 (Forbidden)
(some irrelevant frontend stuff was snipped here)
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:35.771Z [storage-webdav] Load error https://SERVERNAME.TLD/remote.php/webdav/folder/file.kdbx?requesttoken=averylongtokenhere 403 308ms
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:35.772Z [open:/folder/file.kdbx on SERVERNAME.TLD] Storage load error HTTP status 403
keeweb?config=config?file=%2FFOLDER%2FFILE.kdbx:1 2023-08-14T09:38:35.773Z [open-view] Error opening file HTTP status 403
