Persistent Error Message: Could not open from remote, using offline cached version

[Dellow1]

I store my database files on Dropbox. I have no problem setting up credentials for KeeAnywhere with Dropbox, and when I press the connect button, it says it's successful. But when I start Keepass and enter my password, I always get the following error message:

KeeAnywhere Offline Cache:
Could not open from remote, using offline cached version:
dropbox:///G E/Apps/database.kdbx
The decryption operation failed, see inner exception.

This is truly frustrating as when I add new entries, they're just added to the cached version and not to the dropbox version that I access with multiple devices. Please help... otherwise a great plugin!

[Dellow1]

With regard to the above comment, I have the latest version of the plugin and Keepass portable.

[leftdisconnected]

The configuration you describe appears to be correct. I also use Dropbox with a portable copy of KeePass and KeeAnywhere has worked reliably for me for years.

I've not seen the "The decryption operation failed, see inner exception" message before, but my searches suggest that this could be a .NET issue. Kyrodan or someone with expertise may need to help with this.

I found a similar issue mentioned in the KeePass Sourceforge discussions and quoting KeePass guru Paul's post here:

Have you tried ignoring certificate errors?

Tools > Options > Advanced
Scroll down to File Input/Output Connections
Select Accept invalid SSL certificates

I seriously doubt that this will solve your problem, but good luck. Please update with further details if possible, but I don't know how you could find more information about this failure.

[CanadianArtLee]

I get similar problems when trying to connect to my OneDrive stored kdbx files. Running KeePass 2.50 (64-bit) and KeeAnywhere 2.0.3. I can delete and add my cloud drive (OneDrive) successfully. However, when I go to open a file from it (File > Open > Open from Cloud Drive), I get an error message.
Error getting Root node. Exception: Object reference not set to an instance of an object.

[Dellow1]

I'm getting the same message whenever I try to use KeeAnywhere to open any Cloud service.  I've tried Amazon, Google, and Dropbox. I don't have this problem with the Android version of KeePass. I'm afraid I'm going to have to switch to another password keeper.

…

On 1/28/2022 11:44 AM, CanadianArtLee wrote: I get similar problems when trying to connect to my OneDrive stored kdbx files. Running KeePass 2.50 (64-bit) and KeeAnywhere 2.0.3. I can delete and add my cloud drive (OneDrive) successfully. However, when I go to open a file from it (File > Open > Open from Cloud Drive), I get an error message. Error getting Root node. Exception: Object reference not set to an instance of an object. — Reply to this email directly, view it on GitHub <#326 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVALJFCIC5QL4NC536BLSALUYLBXVANCNFSM5MLZRXWQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[josfire18]

I just wanted to add my experience:

I had the error "Object reference not set to an instance of an object" upon entering the password to my database (hosted on onedrive)

It would then say that it was unable to open the database file and was using a cached copy.

I went into KeeAnywhere settings and attempted to add another database, selecting the onedrive option.

It prompted for login and I authenticated.

It then said that there was already a onedrive account associated so it would just update account configuration.

Attempted to login afterwards, without error.

My assumption is my login became invalidated after so many months and it needed to be refreshed with a relogin. Password had not changed.

HTH!