caspadan

I am a Windows user, so I can't help you step-by-step. However, the error mentions a newer version of KeePass is required for the plugin. Taking a look at KeePassRPC changes, it is mentioned in v1.15 of the plugin: "Requires KeePass 2.48+", meaning all versions from 1.15 up require at least KeePass 2.48 to function. You are using 2.47.

I do not use KeePassHTTP plugin, but it loaded fine with 2.57. I also use Vivaldi. But I don't use the plugin, and I assume i need a browser extension of sorts. But I'm in a rush as I need to leave work now. But I found this: See here: https://github.com/pfn/keepasshttp/?tab=readme-ov-file#http-listener-error-message This error occurs because you have multiple copies of KeePassHttp in your KeePass directory! Please check all PLGX- and DLL-files in your KeePass directory and all sub-directories whether...

KeePass2Android stores a "cache" copy of the database. So, it's likely that there was some small change made to this copy or to the file you originally opened. There's no need to panic. KeePass2Android speichert eine "Cache" - Kopie der Datenbank. Es ist also wahrscheinlich, dass an dieser Kopie oder an der Datei, die Sie ursprünglich geöffnet haben, eine kleine Änderung vorgenommen wurde. Da braucht man nicht in Panik zu geraten.

HI, I don't use dropbox myself, but I just tried to open a file from dropbox in KeePass2Android and i managed to sign in to my account and give K2A permission. and I was in and able to open my database. It's unclear what error you are getting. Have you tried saving a copy of your database to onedrive / google drive perhaps and tried opening it from K2A from those providers to see if you still have problems or if it is only with dropbox.

post deleted - disregard It worked for me with and without plugins.

I tested, and it opened in my default browser (Vivaldi). I also have KeepassRPC, but tested without KeePassRPC, and still it does not open in Edge. What other plugins do you have? I have a couple, so can look at what you have to compare and find if there is a culprit maybe.

Then it looks like it was not able to recover the file intact, unfortunately.

Then it looks like it was not able to recover the file intact.